summaryrefslogtreecommitdiffstats
path: root/chpass/edit.c
Commit message (Collapse)AuthorAgeFilesLines
* spdx: initial adoption of licensing ID tags.Pedro F. Giffuni2017-11-181-0/+298
| | | | | | | | | | | | | | | | | The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts. Special thanks to Wind River for providing access to "The Duke of Highlander" tool: an older (2014) run over FreeBSD tree was useful as a starting point. Initially, only tag files that use BSD 4-Clause "Original" license. RelNotes: yes Differential Revision: https://reviews.freebsd.org/D13133
* Create the altix project branch. The altix project will add supportMarcel Moolenaar2010-03-101-296/+0
| | | | | | | 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.
* Avoid clobbering the gecos field, as we intend to use the original later.Dag-Erling Smørgrav2003-04-091-3/+10
| | | | PR: bin/50563
* Use libutil and libypclnt for all passwd manipulation and NIS needs.Dag-Erling Smørgrav2002-05-081-113/+133
| | | | Sponsored by: DARPA, NAI Labs
* Minor post warns stuff.David Malone2002-03-301-3/+5
| | | | | | | | | 1) Fix up vendor IDs for files I'm touching and put FBSDID in the right place. 2) Cast return value of snprintf to size_t rather than casting sizeof() to an int, 'cos we know snprintf returns a non-genative number. 3) Avoid 'char *blank = "";' by just strduping. This could be bad sometimes, but all these variables usually point at malloced memory so this makes them always point at malloced memory.
* Fix warns, ANSIfy, use __FBSDID(), sort headers.Mark Murray2002-03-241-11/+8
|
* Prevent chpass(1) from writing -1 in the UID or GID fieldsMike Barcroft2001-07-261-5/+7
| | | | | | | | | in the password file by properly casting integers. PR: 27757 Reviewed by: des Approved by: des MFC after: 4 days
* Add nsswitch support. By creating an /etc/nsswitch.conf file, you canJacques Vidrine2000-09-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Use an MD5 checksum to test for file changes; the previous methodSheldon Hearn2000-04-121-1/+8
| | | | | | | | | of using file mtimes could result in chpasss(1) erroneously detecting that no changes were made for non-interactive edits. PR: 4238 Reported by: Jens Schweikhardt <schweikh@noc.dfn.de> Submitted by: Daniel Hagan <dhagan@cs.vt.edu>
* Extra sanity checks in information from file edited by user. ThisWarner Losh1999-12-211-16/+16
| | | | | | | precludes using chfn, et al, to generate a divot in /etc. Submitted by: Lukasz Luzar Forgotten about for months by: imp
* $Id$ -> $FreeBSD$Peter Wemm1999-08-281-1/+1
|
* More egcs warning fixes:Warner Losh1999-04-251-2/+2
| | | | | | | | | | 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
* Change the prompt for the office location field from "Location:"Guy Helmer1999-02-231-2/+2
| | | | | | | | | | | | | | to "Office Location:" to disambiguate what is expected. Add a note to the man page to indicate that the office location and office phone fields are concatenated and printed with the heading "Office:" by finger(1). Swap the order of the home and office phone fields in the man page to match the order of the fields in the editor. If any programs interact with chpass(1) and expect "Location:" instead of "Office Location:" as the prompt, either this change will have to be reverted or the other programs will have to be changed. PR: docs/7533
* Tweaks to allow compiling -Wall (mostly adding "const" to char rcsid[]).Archie Cobbs1998-12-061-2/+2
|
* Submitted by: Peter Hawkins <thepish@FreeBSD.org>Peter Hawkins1998-08-141-4/+11
| | | | | | 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.
* Free a malloc'ed variable before exiting. Compute line number when parsingPhilippe Charnier1997-06-251-4/+10
| | | | | input file, it helps finding errors. Obtained from: OpenBSD.
* pw_scan() was being used to convert a string into a struct passwd, withPeter Wemm1996-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 new option to chpass: -e "expire" ; change the account expire timePeter Wemm1996-08-121-0/+3
| | | | | | | | | | | | | | | 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.
* Add missing semicolon so that this module compiles whithout -DYP.Bill Paul1996-06-151-1/+1
| | | | Submitted (via Usenet) by: Nathan Torkington <gnat@frii.com>
* Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs.Bill Paul1996-02-231-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Take the ypchfn/ypchsh stuff that was removed from passwdBill Paul1995-08-131-1/+9
| | | | | | | | | | | | | | | | | | | 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.)
* Remove trailing whitespace.Rodney W. Grimes1995-05-301-3/+3
|
* Bug fixed: even root was unable to edit restricted fieldsAndrey A. Chernov1995-03-211-4/+4
|
* Fixes for chpass.Jordan K. Hubbard1995-02-091-8/+24
| | | | Submitted by: Heikki Suonsivu <hsu@cs.hut.fi>
* BSD 4.4 Lite Usr.bin SourcesRodney W. Grimes1994-05-271-0/+213