| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
uid and gid are never and should never be negative. The pw(8) manpage clearly
states the -u and -g arguments are for uids/gids, hence using negative values is
abusing a bug in former versions of pw(8)
|
|
|
|
|
| |
PR: 196514
MFC after: 1 week
|
|
|
|
|
|
| |
Check the uid passed is actually a number as early as possible
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
The user was perperly adding the to different groups from "list" but was not
removed from the other groups it could have belong to.
While here add a regression test about this bug
PR: 185666
Reported by: sub.mesa@gmail.com
MFC after: 1 week
|
|
|
|
|
|
| |
in r252688.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
Previuosly given 'foo,bar' members, removing 'foo' would result in an
infinite loop.
PR: 191427
Submitted by: Voradesh Yenbut <yenbut cs.washington.edu>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
is not associated with user "username". E.g., user "foo" has primary group
"wheel" and is unassociated with group "foo", yet userdel would delete the
group "foo" when deleting user "foo" (despite the fact that user "foo" is
not associated with group "foo" in any way).
Patch committed with minor style(9) changes.
PR: bin/169471
Submitted by: Alexander Pyhalov <apyhalov@gmail.com>
|
|
|
|
|
|
|
|
| |
Don't let pw crash when give certain input.
PR: 187310
Submitted by: Kim Shrier
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
date to the current date.
MFC after: 3 days
|
|
|
|
| |
Submitted by: dt71@gmx.com
|
|
|
|
| |
a user whose group != username.
|
| |
|
| |
|
|
|
|
| |
Submitted by: Christoph Mallon <christoph.mallon@gmx.de>
|
|
|
|
|
|
| |
terminator is j + 2.
Submitted by: Christoph Mallon <christoph.mallon@gmx.de>
|
|
|
|
| |
Reported by: "Sam Fourman Jr." <sfourman@gmail.com>, dim
|
|
|
|
|
|
| |
Submitted by: db
Approved by: cperciva
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 months
|
|
|
|
| |
Reported by: Robert Bonomi <bonomi@mail.r-bonomi.com>
|
|
|
|
|
|
|
|
|
| |
number.
This also allow pw user show to work as expected.
PR: bin/172112
Submitted by: "Ilya A. Arkhipov" <rum1cro@yandex.ru>
MFC after: 1 month
|
| |
|
|
|
|
|
|
| |
ptrdiff_t.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
historic behavior (create the default base directory in pw.conf) before
I came up with a better fix for this.
Requested by: nwhitehorn
Approved by: re (kib)
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
| |
for the SGI Altix 350 to FreeBSD/ia64. The hardware used for porting
is a two-module system, consisting of a base compute module and a
CPU expansion module. SGI's NUMAFlex architecture can be an excellent
platform to test CPU affinity and NUMA-aware features in FreeBSD.
|
|
|
|
|
|
| |
The size of the username record in utmp files should not influence the
maximum username length. Right now ut_user/ut_name is big enough, so in
this case it's dead code anyway.
|
|
|
|
|
|
| |
Remove pw_getrand() unneded now: arc4random_uniform() is stronger then
pw_getrand()'s MD5 tricks (inactive) and its active version, mixing
arc4random() bytes in one, not make things better at all.
|
|
|
|
|
|
|
|
|
|
|
| |
This makes blowfish password hashes look normal when set using
pw(8)/adduser(8). [1]
- Make it possible to have a '/' in the salt.
PR: 121146 [1]
Submitted by: Jaakko Heinonen [1]
Approved by: rwatson (mentor)
MFC after: 1 month
|
|
|
|
| |
PR: bin/53434
|
|
|
|
| |
more specific about the effect of the current umask on -M.
|
|
|
|
|
|
|
|
| |
the user's newly created home directory. If omitted, it's derived
from the current umask.
PR: bin/16880, bin/83253 (partially), bin/104248
MFC in: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previous symlink was confusing:
# cd /jails/virtual_system_1/home
# realpath .
/usr/home
...and slower.
OK'ed by: rwatson, phk
|
|
|
|
|
|
|
| |
strncpy(d, s, l);
d[l - 1] = '\0';
statements.
|
|
|
|
|
|
|
|
| |
-d option was equal to the one already saved and which caused
the pw utility to avoid updating values passed by other options
processed before the -d option in the code path.
Spotted by: Richard Caley <rjc@interactive.co.uk>
|
|
|
|
|
|
|
| |
encrypted password on the specified file descriptor.
PR: bin/22033
MFC after: 2 weeks
|
|
|
|
| |
Switch to arc4random() completely.
|
|
|
|
|
|
|
|
|
|
|
| |
or group name (mainly for the benefit of samba). This pretty much rewrites
he pw_checkname() routine, but should work exactly the same except for the
above change, and that error messages are somewhat more informative.
PR: 28733 46890
Inspired by: example patch written by Terry Lambert
Reviewed by: no objections on freebsd-arch and freebsd-current
MFC plans: no plans, but will do if people want it in stable.
|
|
|
|
|
|
|
|
| |
that can be fixed when the many other warnings here are being fixed.)
PR: 39741
Submitted by: Dan Lukes <dan@obluda.cz>
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
| |
mail, if configured to do so. Some sites have setups where the user's
mail is delivered to their home directory, so sending mail before is
exists didn't work.
PR: 29892
|
|
|
|
|
|
|
| |
Right now, the automatically generated passwords have been rather
predictable. :-(
MFC after: 1 day
|
|
|
|
|
|
| |
USE_MD5RAND.
MFC after: 2 days
|
| |
|
|
|
|
|
|
| |
(random() or arc4random())
Reviewed by: bde
|
|
|
|
|
|
| |
structure internals.
Reviewed by: markm
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for crypt(3) by now. In any case:
Add crypt_set_format(3) + documentation to -lcrypt.
Add login_setcryptfmt(3) + documentation to -lutil.
Support for switching crypt formats in passwd(8).
Support for switching crypt formats in pw(8).
The simple synopsis is:
edit login.conf; add a passwd_format field set to "des" or "md5"; go nuts :)
Reviewed by: peter
|
|
|
|
|
|
|
| |
This should cause -w's argument not to be ignored in the usermod case,
so it will affect modification of the user's password instead of using
the pw.conf (or internal default=no '*') password method.
PR: bin/11168
|
|
|
|
|
| |
no default group (and thus fall back to user-based groups instead).
PR: bin/5717
|
|
|
|
|
|
| |
-h - to set no password. But only mark modified if the account is not
already locked (i.e. first char of crypt password field is '*').
PR: bin/19999
|