9 Commits

Author SHA1 Message Date
peter
cc8565d1c5 Unifdef -DPASSWD_IGNORE_COMMENTS. This wasn't really optional and
we have enough pseudo-options already.
1999-09-06 17:30:03 +00:00
sheldonh
bc7c4b861c Allow comments and blank lines as advertised in passwd(5).
PR:	12828
Submitted by:	Yasuhiro Fukuma <yasuf@big.or.jp>
1999-07-29 16:30:35 +00:00
imp
22f901a57c More egcs warning fixes:
o main returns int not void
	o use return 0 at end of main when needed
	o use braces to avoid potentially ambiguous else
	o don't default to type int
	o #ifdef 0 -> #if 0

Reviewed by: obrien and chuckr
1999-04-25 22:37:58 +00:00
bde
2625896b1b Fixed printf format errors. Assume that time_t's are representable as
longs.
1998-10-17 14:06:20 +00:00
markm
9a65690bbf Quieten -Wall. 1997-09-28 08:46:12 +00:00
wpaul
eea42f60d4 *blush* Whoops: got the format strings wrong. 1996-10-22 03:43:34 +00:00
wpaul
36f3371a8f Part 2 of fix for PR #1519. The problem here is similar to what
was going on in pwd_mkdb, except here we also have to deal with
the pw_change and pw_expire fields.
1996-10-22 03:27:12 +00:00
wpaul
34376c5be4 Take the ypchfn/ypchsh stuff that was removed from passwd
and graft it into chpass.

Chpass can now tell when it's being asked to operate on an NIS
user and it displayes the appropriate message in the editor
template ("Changing NIS information for foo"). After the changes
have been made, chpass will promte the user for his NIS password.
If the password is correct, the changes are committed to yppasswdd.

Hopefully, this should make NIS more transparent to the end user.

Note that even the superuser needs to know a user's password before
he can change any NIS information (such is the nature of yppasswdd).
Also, changes to the password field are not permitted -- that's what
yppasswd is for. (The superuser may specify a new password, but
again, he needs to know the user's original password before he can
change it.)
1995-08-13 16:12:28 +00:00
rgrimes
f9ab90d9d6 BSD 4.4 Lite Usr.bin Sources 1994-05-27 12:33:43 +00:00