summaryrefslogtreecommitdiffstats
path: root/chpass/pw_copy.c
Commit message (Collapse)AuthorAgeFilesLines
* Quieten -Wall.Mark Murray1997-09-281-1/+2
|
* *blush* Whoops: got the format strings wrong.Bill Paul1996-10-221-4/+4
|
* Part 2 of fix for PR #1519. The problem here is similar to whatBill Paul1996-10-221-8/+25
| | | | | was going on in pwd_mkdb, except here we also have to deal with the pw_change and pw_expire fields.
* Take the ypchfn/ypchsh stuff that was removed from passwdBill Paul1995-08-131-0/+8
| | | | | | | | | | | | | | | | | | | 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.)
* BSD 4.4 Lite Usr.bin SourcesRodney W. Grimes1994-05-271-0/+107