summaryrefslogtreecommitdiffstats
path: root/usr.bin/chpass
Commit message (Collapse)AuthorAgeFilesLines
* Fixed disordering of cross references in previous commit.bde1998-12-131-3/+3
|
* Add reference to login.conf(5)dillon1998-12-131-2/+3
|
* PR: docs/9045dillon1998-12-131-27/+31
| | | | | | Update chpass(1) manual page. Change the definition of the class field and also reorganize the field list to match that of the /etc/master.passwd file, to avoid confusion.
* Tweaks to allow compiling -Wall (mostly adding "const" to char rcsid[]).archie1998-12-065-10/+11
|
* Fixed printf format errors. Assume that uid_t's are representable asbde1998-10-171-2/+2
| | | | unsigned longs.
* Fixed printf format errors. Assume that time_t's are representable asbde1998-10-171-2/+2
| | | | longs.
* Remove useless `BINOWN=root' now that it is the default.obrien1998-09-191-1/+0
|
* Bump up the E_SHELL constant after an extra field was added, thus makingmarkm1998-09-031-1/+1
| | | | | this refer to the wrong data. Submitted by: axl@iafrica.com (Sheldon Hearn)
* Submitted by: Peter Hawkins <thepish@freebsd.org>thepish1998-08-141-5/+9
| | | | Document last mod (extended gcos)
* Submitted by: Peter Hawkins <thepish@FreeBSD.org>thepish1998-08-143-4/+13
| | | | | | Add functionality for support for more than 4 subfields within gcos. chsh, chpass etc did not parse beyond the 4th field previously and so truncated gcos on updating the database.
* Correct the description of the last four fields.steve1998-06-131-3/+3
| | | | | PR: 6926 Submitted by: Josh Gilliam <josh@quick.net>
* Fixed `make -j9' by putting generated headers in ${SRCS}. Removed bogusbde1998-04-261-10/+10
| | | | | dependencies of generated .c files on generated headers (these made `make -JN' work provided `depend' was made first). Sorted sources lists.
* Add rcsid. Correct -Wall warning.charnier1998-03-231-1/+5
|
* Removed extra (non-trailing) arg in a call to warnx().bde1997-12-181-2/+2
|
* Quieten -Wall.markm1997-09-281-1/+2
|
* Add manpage links ypchpass.1, ypchfn.1, ypchsh.1wosch1997-09-131-0/+3
|
* Modify passwd and chpass to use new AF_LOCAL RPC interface instead ofwpaul1997-07-292-17/+23
| | | | old kludged-up 'yppasswd_comm' support.
* Free a malloc'ed variable before exiting. Compute line number when parsingcharnier1997-06-252-5/+12
| | | | | input file, it helps finding errors. Obtained from: OpenBSD.
* Fix for PR #3141: check for NULL before strdup()ing pw->pw_class.wpaul1997-03-291-2/+3
| | | | | | | | | (I'm not sure why this happens, though I suspect it may be because the server is configured with only passwd maps instead of both passwd and master.passwd maps. This is allowed, but I think in this case pw_class is left NULL, hence the problem.) Also applied similar patch to chpass/pw_yp.c just for paranoia's sake.
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-3/+3
| | | | posix standard on the topic.
* If an administrator somehow manages to break the hardlinksmpp1997-02-261-2/+4
| | | | | | | | | | | | on chpass & passwd and turn the links into individual files with the schg flag set, make install will fail to install all of the proper links. Fixed by removing the schg flag on all of the links before installing. Closes PR# 2040. Submitted by: Ph. Charnier <charnier@xp11.frmug.org>
* Revert $FreeBSD$ to $Id$peter1997-02-223-3/+3
|
* Sort cross references.wosch1997-01-151-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-143-3/+3
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* pw_scan() was being used to convert a string into a struct passwd, withpeter1996-11-151-1/+1
| | | | | | | | | | | an auto stack variable that was about to disappear. It broke with some nis passwd changes because of a gethostbyname() call that uses a fair bit of stack.. This was a timebomb waiting to go off at any time and could have been causing subtle corruption for a while. AARGH!! This is HIGHLY reccomended for 2.2 and presumably 2.1.6
* Add a flag to allow the 'use NIS or local?' logic to tell when NIS iswpaul1996-10-232-5/+8
| | | | | | | enabled in /etc/master.passwd & friends. This allows the 'USER_YP_AND_LOCAL' case to make a more sensible guess (if NIS is enabled, default to NIS, otherwise default to local -- this is better than defaulting to NIS all the time).
* *blush* Whoops: got the format strings wrong.wpaul1996-10-221-4/+4
|
* Part 2 of fix for PR #1519. The problem here is similar to whatwpaul1996-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.
* Modify the 'couldn't create udp handle' message so it tell youwpaul1996-10-221-4/+5
| | | | | | the name of the host that couldn't be connected to. This will hopefully make it easier to diagnose problems with certain NIS configuration problems.
* Add new option to chpass: -e "expire" ; change the account expire timepeter1996-08-125-13/+38
| | | | | | | | | | | | | | | from a script as if it was done in the interactive editor. When reassembling the gecos string, trim any excess trailing commas, they look ugly in the passwd file. :-) Have a simple Makefile tweak to prevent mortal users from changing their fullname. As ISP's we have seem some real bizzare stuff here.. When decoding the change/expire string, allow the month number as a synonym for the name of the month.. (ie: 1 as well as Jan or January) Note that using numbers means there's a chance that you can get bitten if you're not used to the American DD-MM-YY order.
* Move setting of username to the correcft place; also initialize it.guido1996-07-141-3/+3
| | | | Reviewed by: peter@freebsd.org
* Implement incremental passwd database updates. This is done by ading a '-u'guido1996-07-011-2/+4
| | | | | | | | | | | | | | option to pwd_mkdb and adding this option to utilities invoking it. Further, the filling of both the secure and insecure databases has been merged into one loop giving also a performance improvemnet. Note that I did *not* change the adduser command. I don't read perl (it is a write only language anyway). The change will drastically improve performance for passwd and friends with large passwd files. Vipw's performance won't change. In order to do that some kind of diff should be made between the old and new master.passwd and depending the amount of changes, an incremental or complete update of the databases should be agreed upon.
* Add missing semicolon so that this module compiles whithout -DYP.wpaul1996-06-151-1/+1
| | | | Submitted (via Usenet) by: Nathan Torkington <gnat@frii.com>
* Fix the -l flag. For some reason I can't fathom, I left in some codewpaul1996-05-251-8/+5
| | | | | | that would cause it to fail if anyone but the superuser tried to use it. Also fix a couple of harmless typos since I'm in the area.
* In use_yp(), call _yp_check() to make ultra, super-duper sure that NISwpaul1996-05-071-2/+3
| | | | | | | is available before trying to go hunting for a domain name. This fixes the following problem: you have +::::::::: in /etc/master.passwd but NIS isn't running (no ypbind, no domain name set) -- passwd and chpass will still try to change an NIS password instead of the local one.
* Print some warnings if root invokes chpass and sets thempp1996-04-111-0/+19
| | | | | | | | | | | | | | | | | shell to one of the following: - a non-existent file - a non-regular file - a file without any execute bits set The shell is still set to whatever they entered even if the above conditions exist (hey, it is the super user doing this after all :-), but this might give the admin. some warning that they are about to screw themselves and give them a chance to fix it before it is too late. Inspired by: some new FreeBSD user on USENET who set his root shell to a shell that doesn't exist and now can't gain access to root (don't worry, I sent him some mail on how to recover from this).
* Fix small bug in get_yp_master(): this function is used to look forwpaul1996-03-041-1/+13
| | | | | | | | | | a master server and initialize the suser_override flag, but in a non-NIS environment is should be smart enough to just leave the flag cleared and return (unless forced with a command-line argument like -y). Otherwise, it will return an NIS-related error even if NIS isn't turned on. Pointed out by: ache
* Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs.wpaul1996-02-236-144/+504
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
* Fix typo in xref in NOTES section.mpp1996-02-141-1/+1
|
* Move the YP initialization earlier, so it's done before the evaluationjoerg1996-01-061-26/+27
| | | | | | of -p/-s/-a related cruft. Closes PR # misc/933 "chpass -s <shell>" does not work
* Correct a typo :-).ats1995-09-021-1/+1
|
* Make use_yp() smarter about figuring out whether a user is local orwpaul1995-09-024-30/+202
| | | | | | | | | | NIS (or both, or neither). Also add support for -l and -y flags to force behavior to local or NIS. use_yp() also goes out of its way to retrieve the correct password database information (local or NIS) depending on what the situation since getpwent() & co. can't necessarily be trusted in some cases. Also document new flags in man page.
* Remove bogus ${DESTDIR}s from LINKS.bde1995-08-171-8/+10
| | | | | | | Keep DPADD up to date with LDADD. bsd.prog.mk's install rule can't handle schg'ed links, so ugly beforeinstall and afterinstall rules are required.
* Take the ypchfn/ypchsh stuff that was removed from passwdwpaul1995-08-137-9/+421
| | | | | | | | | | | | | | | | | | | 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.)
* Delete bogus referneces to timezone code internal header file `tzfile.h',wollman1995-08-071-5/+4
| | | | which is no longer bogusly installed in /usr/include.
* Fix chpass so that it doesn't advance the passwordmpp1995-07-161-11/+9
| | | | | change and expire dates by 1 day anytime root edits a user that has a change/expire date set.
* Somewhere along the line, somebody decided to make the 'full name' fieldwpaul1995-06-231-1/+1
| | | | | | | | | | | | restricted. Am I the only one who sees the absurdity of having chfn be a link to chpass, and then denying users permission to use chpass to change their full names? Of course, chpass has a much more severe bug in it, which is that it allows users to change their password database info without first asking them for their password. I hope to fix this at some point so that I can merge ypchpass, ypchfn, ypchsh and chpass into one program (password authentication is required for changing NIS data).
* Remove trailing whitespace.rgrimes1995-05-304-8/+8
|
* Missing ${DESTDIR} on chflags commands added.rgrimes1995-04-171-2/+3
|
* Bug fixed: even root was unable to edit restricted fieldsache1995-03-211-4/+4
|
OpenPOWER on IntegriCloud