#
05f98035 |
| 17-Apr-2003 |
Jacques Vidrine <nectar@FreeBSD.org> |
= Implement thread-safe versions of the getpwent(3) and getgrent(3) family of functions using the new nsdispatch(3) core. Remove arbitrary size limits when using the thread-safe versions.
= Re-
= Implement thread-safe versions of the getpwent(3) and getgrent(3) family of functions using the new nsdispatch(3) core. Remove arbitrary size limits when using the thread-safe versions.
= Re-implement the traditional getpwent(3)/getgrent(3) functions on top of the thread-safe versions.
= Update the on-disk format of the hashed version of the passwd(5) databases to allow for versioned entries. The legacy version is `3'. (Don't ask.)
= Add support for version `4' entries in the passwd(5) database. Entries in this format are identical to version 3 entries except that all integers are stored as 32-bit integers in network byte order (big endian).
= pwd_mkdb is updated to generate both version 3 and version 4 entries.
Sponsored by: DARPA, Network Associates Laboratories
show more ...
|
Revision tags: release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1 |
|
#
2f9af241 |
| 11-Jul-2002 |
Alfred Perlstein <alfred@FreeBSD.org> |
WARNS=4 cleanup, de-__P()
|
Revision tags: release/4.6.0_cvs |
|
#
524a875c |
| 09-Mar-2002 |
Dima Dorfman <dd@FreeBSD.org> |
When reporting that a line is too long, include the line number in the error message. While I'm here, add a note that the "line too long" message isn't always accurate.
PR: 35395 Submitted by: and
When reporting that a line is too long, include the line number in the error message. While I'm here, add a note that the "line too long" message isn't always accurate.
PR: 35395 Submitted by: andrew@ugh.net.au
show more ...
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
#
9213df7c |
| 27-Oct-2001 |
Peter Wemm <peter@FreeBSD.org> |
Explicitly use int32_t for on-disk records for pw_change and pw_expire, since that is what we use now and this insulates us from any time_t tweaks here. We can define a record format that uses 64 bi
Explicitly use int32_t for on-disk records for pw_change and pw_expire, since that is what we use now and this insulates us from any time_t tweaks here. We can define a record format that uses 64 bit times if/when we need to.
show more ...
|
Revision tags: release/4.3.0_cvs, release/4.3.0, release/4.2.0, release/4.1.1_cvs |
|
#
248aee62 |
| 06-Sep-2000 |
Jacques Vidrine <nectar@FreeBSD.org> |
Add nsswitch support. By creating an /etc/nsswitch.conf file, you can configure FreeBSD so that various databases such as passwd and group can be looked up using flat files, NIS, or Hesiod.
= Hesio
Add nsswitch support. By creating an /etc/nsswitch.conf file, you can configure FreeBSD so that various databases such as passwd and group can be looked up using flat files, NIS, or Hesiod.
= Hesiod has been added to libc (see hesiod(3)).
= A library routine for parsing nsswitch.conf and invoking callback functions as specified has been added to libc (see nsdispatch(3)).
= The following C library functions have been modified to use nsdispatch: . getgrent, getgrnam, getgrgid . getpwent, getpwnam, getpwuid . getusershell . getaddrinfo . gethostbyname, gethostbyname2, gethostbyaddr . getnetbyname, getnetbyaddr . getipnodebyname, getipnodebyaddr, getnodebyname, getnodebyaddr
= host.conf has been removed from src/etc. rc.network has been modified to warn that host.conf is no longer used at boot time. In addition, if there is a host.conf but no nsswitch.conf, the latter is created at boot time from the former.
Obtained from: NetBSD
show more ...
|
Revision tags: release/4.1.0, release/3.5.0_cvs, release/4.0.0_cvs |
|
#
cd7b8d78 |
| 09-Mar-2000 |
Paul Richards <paul@FreeBSD.org> |
Fix various unsigned vs signed errors that caused problems with uids and gids bigger than 16 bits. Added checks for uids and gids that are bigger than 32 bits.
Approved by: jkh (partly, this fix is
Fix various unsigned vs signed errors that caused problems with uids and gids bigger than 16 bits. Added checks for uids and gids that are bigger than 32 bits.
Approved by: jkh (partly, this fix is bigger than I first intended)
show more ...
|
Revision tags: release/3.4.0_cvs |
|
#
9a602acc |
| 02-Dec-1999 |
Sheldon Hearn <sheldonh@FreeBSD.org> |
Replace the -q option to pwd_mkdb with a test for PW_SCAN_BIG_IDS in the environment. This allows big ID warnings to be suppressed for vipw and chpass as well.
Since the environment variable test i
Replace the -q option to pwd_mkdb with a test for PW_SCAN_BIG_IDS in the environment. This allows big ID warnings to be suppressed for vipw and chpass as well.
Since the environment variable test is only performed for callers of pw_scan() that do not set pw_big_ids_warning, the test can still be overriden. Currently, chpass and pwd_mkdb are the only users of pw_scan() and neither of them overrides the environment variable test.
show more ...
|
#
18138b08 |
| 15-Nov-1999 |
Sheldon Hearn <sheldonh@FreeBSD.org> |
Add to pwd_mkdb a -q option to silence warnings about large IDs. Add a suitably ominous warning in the manual page.
The diff applied is not the one provided in the attributed PR.
PR: 13344 Review
Add to pwd_mkdb a -q option to silence warnings about large IDs. Add a suitably ominous warning in the manual page.
The diff applied is not the one provided in the attributed PR.
PR: 13344 Reviewed by: bde
show more ...
|
Revision tags: release/3.3.0_cvs |
|
#
0c2b3c31 |
| 06-Sep-1999 |
Peter Wemm <peter@FreeBSD.org> |
Unifdef -DPASSWD_IGNORE_COMMENTS. This wasn't really optional and we have enough pseudo-options already.
|
#
97d92980 |
| 28-Aug-1999 |
Peter Wemm <peter@FreeBSD.org> |
$Id$ -> $FreeBSD$
|
Revision tags: release/3.2.0, release/3.1.0, release/3.0.0, release/2.2.8 |
|
#
0be7a84b |
| 01-Jan-1999 |
Bill Fumerola <billf@FreeBSD.org> |
Enable source file locking in pwd_mkdb by including the proper letter in getopt(). The code was there, the means to use it wasn't.
Also update the usage() statment to reflect reality.
PR: bin/9248
Enable source file locking in pwd_mkdb by including the proper letter in getopt(). The code was there, the means to use it wasn't.
Also update the usage() statment to reflect reality.
PR: bin/9248 Submitted by: Jos Backus <jbackus@plex.nl> Forgotten By: dillon
show more ...
|
#
be648216 |
| 13-Dec-1998 |
Matthew Dillon <dillon@FreeBSD.org> |
PR: bin/3478
Have pwd_mkdb lock the source file while rebuilding the database. When called by programs such as vipw, the source file is a temporary file and this does not conflict with
PR: bin/3478
Have pwd_mkdb lock the source file while rebuilding the database. When called by programs such as vipw, the source file is a temporary file and this does not conflict with the lock on /etc/master.passwd already held by vipw. When run manually, however, master.passwd is typically specified as the argument and the locking prevents other programs from messing with master.passwd during the database rebuild.
Also pwd_mkdb uses a blocking exclusive lock as it may be called from a script. The -N option was added to cause pwd_mkdb to get the lock non-blocking and exit with an error if the attempt fails, again useful for scripts.
show more ...
|
#
17b09aca |
| 12-Dec-1998 |
Foxfair Hu <foxfair@FreeBSD.org> |
Close PR bin/8753 pwd_mkdb problem when having comments in passwd file
Submitted by Chia-liang Kao clkao@CirX.ORG .
|
#
50819461 |
| 29-Sep-1998 |
Dmitrij Tejblum <dt@FreeBSD.org> |
Rename a static variable, so it will not shadowed by a local variable. Now comments will be ignored, rather than put junk in the password database.
Broken in: rev. 1.21
|
Revision tags: release/2.2.7 |
|
#
5c9f7df5 |
| 09-Jun-1998 |
Andrey A. Chernov <ache@FreeBSD.org> |
Fix usage string
|
#
e6bb224e |
| 19-Apr-1998 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Allow specification of cache-size to pwd_mkdb PR: 5193 Reviewed by: phk Submitted by: Nick Hilliard <nick@foobar.org>
|
Revision tags: release/2.2.6 |
|
#
51600569 |
| 19-Feb-1998 |
Guido van Rooij <guido@FreeBSD.org> |
Reenable building of /etc/passwd. Pointed out by: "Julie M. Juracich" <julie@xaqti.com>
|
#
cf564323 |
| 16-Feb-1998 |
Guido van Rooij <guido@FreeBSD.org> |
Apparently, if fprintf() fails, it can return any negative value Pointed out by: Bruce
|
#
1aa9837c |
| 15-Feb-1998 |
Guido van Rooij <guido@FreeBSD.org> |
Check return values of fprintf, fclose (this one is overdone I guess) and pw_db->close. PR: 4202 (probably, I askd the submitter) Obtained from: OpenBSD
|
#
d7f71209 |
| 10-Jan-1998 |
Wolfram Schneider <wosch@FreeBSD.org> |
Rename the pwd_mkdb(8) option '-c' to '-C' for better compatiblity with BSD/OS.
|
Revision tags: release/2.2.5_cvs |
|
#
8b76e1d7 |
| 10-Oct-1997 |
Philippe Charnier <charnier@FreeBSD.org> |
Staticize usage(). Cosmetics.
|
#
7256f6b3 |
| 18-Aug-1997 |
Jonathan Lemon <jlemon@FreeBSD.org> |
db close routine actually writes data out to disk; return value was not being checked. Change code to fail if db->close errors.
PR: 4202
|
Revision tags: release/2.2.2_cvs |
|
#
6c3f552a |
| 31-Mar-1997 |
Warner Losh <imp@FreeBSD.org> |
compare return value from getopt against -1 rather than EOF, per the final posix standard on the topic.
|
Revision tags: release/2.2.1_cvs |
|
#
dc7eb240 |
| 20-Mar-1997 |
David Nugent <davidn@FreeBSD.org> |
Fix possible (not stack) overflow from -d <dir> commandline option.
|
Revision tags: release/2.2.0, release/2.1.7_cvs |
|
#
eb0abfcc |
| 08-Mar-1997 |
Wolfram Schneider <wosch@FreeBSD.org> |
Allow comments in password database. The comments are copied from the password file into /etc/master.passwd and optional (-p) into /etc/passwd. Enable this feature with the compile option -DPASSWD_IG
Allow comments in password database. The comments are copied from the password file into /etc/master.passwd and optional (-p) into /etc/passwd. Enable this feature with the compile option -DPASSWD_IGNORE_COMMENTS.
The character `#' introduces a comment. Leading spaces and tabs are ignored: '^[ \t]*#.*\n$'
Count an empty line - only spaces, tabs or newline - also as a comment. An empty line at the bottom of /etc/master.passwd is a common novice error and increased my mail load: '^[ \t]*\n$'
show more ...
|