summaryrefslogtreecommitdiffstats
path: root/chpass/chpass.1
Commit message (Collapse)AuthorAgeFilesLines
* usr.bin/chpass: Correct manpage regarding path to temp filesCeri Davies2021-05-261-3/+3
| | | | Approved by: blackend (mentor)
* Partially revert r367756 (chpass(1) synopsis changes)Mateusz Piotrowski2020-11-171-1/+7
| | | | | | | | | | | | | | Let's have two entries in the synopsis: - chpass now lists options which can be used for non-NIS-specific functionalities. - ypchpass additionally lists the NIS-specific flags. Technically, it is an artificial distinction, as chpass and ypchpass behave identically. Nevertheless, it might help navigating the synopsis section. Reviewed by: imp MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D27251
* Add an example for the -s flagMateusz Piotrowski2020-11-171-0/+6
| | | | MFC after: 2 weeks
* Improve readability of the lists of optionsMateusz Piotrowski2020-11-171-20/+20
| | | | | | | | - Sort options alphabetically - Add missing arguments (e.g., "list" to -a) - Adjust the width of Bl MFC after: 1 week
* Clean up the synopsis section & fix mandoc warningsMateusz Piotrowski2020-11-171-12/+6
| | | | | | | | The synopsis section had two very similar entries. The flags documented by the first one were a strict subset of the second one. Let's just keep only the second entry for simplicity. MFC after: 1 week
* Renumber copyright clause 4Warner Losh2017-02-281-1/+1
| | | | | | | | | Renumber cluase 4 to 3, per what everybody else did when BSD granted them permission to remove clause 3. My insistance on keeping the same numbering for legal reasons is too pedantic, so give up on that point. Submitted by: Jan Schaumann <jschauma@stevens.edu> Pull Request: https://github.com/freebsd/freebsd/pull/96
* mdoc: minor paragraph fixes.Joel Dahl2014-02-081-0/+485
|
* Create the altix project branch. The altix project will add supportMarcel Moolenaar2010-03-101-492/+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.
* The group field is called `gid', not `group'.Ed Schouten2010-01-141-1/+1
|
* Cross-reference pw(8) into chpass(1), passwd(1), and vipw(8).Sean Chittenden2005-08-021-0/+1
|
* Sort sections.Ruslan Ermilov2005-01-181-2/+2
|
* Remove useless .Pp. Typo: gcos -> gecos (as spelled in passwd(5)).Philippe Charnier2004-07-261-2/+1
|
* Mechanically kill hard sentence breaks.Ruslan Ermilov2004-07-021-2/+4
|
* Typo fix.Marc Fonvieille2004-03-031-1/+1
| | | | | | PR: docs/63677 Submitted by: Volker Stolz <stolz@i2.informatik.rwth-aachen.de> MFC after: 1 week
* mdoc(7) police: Deal with self-xrefs.Ruslan Ermilov2002-12-241-5/+5
|
* mdoc(7) police: more `The .Nm utility' + markup nit.Ruslan Ermilov2002-12-231-5/+5
|
* Move the NOTES section to DESCRIPTION. And correct some documentation whileTom Rhodes2002-12-201-11/+13
| | | | | | | I'm here. PR: 43756 Submitted by: Gary W. Swearingen <swear@attbi.com>
* Use `The .Nm utility'Philippe Charnier2002-04-191-10/+15
|
* mdoc(7) police: s/BSD/.Bx/ where appropriate.Ruslan Ermilov2001-08-141-1/+3
|
* can not -> cannotSheldon Hearn2001-08-081-1/+1
|
* Remove whitespace at EOL.Dima Dorfman2001-07-151-3/+3
|
* mdoc(7) police: remove extraneous .Pp before and/or after .Sh.Dima Dorfman2001-07-091-1/+0
|
* Prepare for mdoc(7)NG.Ruslan Ermilov2000-12-191-1/+1
|
* Use correct macro for path nameAlexey Zelkin2000-11-221-1/+1
| | | | PR: docs/13218
* mdoc(7) police: use the new features of the Nm macro.Ruslan Ermilov2000-11-201-5/+5
|
* Remove more single-space hard sentence breaks.Sheldon Hearn2000-03-021-1/+2
|
* Remove single-space hard sentence breaks. These degrade the qualitySheldon Hearn2000-03-011-10/+20
| | | | | of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
* Document -e flag.Alexey Zelkin1999-12-171-0/+14
| | | | | PR: docs/14936 Submitted by: Stephen J. Roznowski <sjr@home.com>
* Replace the -q option to pwd_mkdb with a test for PW_SCAN_BIG_IDS inSheldon Hearn1999-12-021-0/+6
| | | | | | | | | | | 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.
* mdoc(7)'fyAlexey Zelkin1999-11-181-33/+40
| | | | Mostly submitted by: "Philippe Charnier" <charnier@xp11.frmug.org>
* mdoc(7)'fyAlexey Zelkin1999-10-301-12/+20
|
* $Id$ -> $FreeBSD$Peter Wemm1999-08-281-1/+1
|
* Fix a bunch of broken cross-referencesChris Costello1999-08-181-2/+2
|
* Change the prompt for the office location field from "Location:"Guy Helmer1999-02-231-5/+10
| | | | | | | | | | | | | | 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
* Fixed disordering of cross references in previous commit.Bruce Evans1998-12-131-3/+3
|
* Add reference to login.conf(5)Matthew Dillon1998-12-131-2/+3
|
* PR: docs/9045Matthew Dillon1998-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.
* Submitted by: Peter Hawkins <thepish@freebsd.org>Peter Hawkins1998-08-141-5/+9
| | | | Document last mod (extended gcos)
* Correct the description of the last four fields.Steve Price1998-06-131-3/+3
| | | | | PR: 6926 Submitted by: Josh Gilliam <josh@quick.net>
* Free a malloc'ed variable before exiting. Compute line number when parsingPhilippe Charnier1997-06-251-1/+2
| | | | | input file, it helps finding errors. Obtained from: OpenBSD.
* Sort cross references.Wolfram Schneider1997-01-151-1/+1
|
* Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs.Bill Paul1996-02-231-14/+99
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.Mike Pritchard1996-02-141-1/+1
|
* Correct a typo :-).Andreas Schulz1995-09-021-1/+1
|
* Make use_yp() smarter about figuring out whether a user is local orBill Paul1995-09-021-1/+22
| | | | | | | | | | 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.
* Take the ypchfn/ypchsh stuff that was removed from passwdBill Paul1995-08-131-1/+77
| | | | | | | | | | | | | | | | | | | 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.)
* Add a `-p' option, allowing the super-user to directly set a user'sGarrett Wollman1995-01-141-1/+9
| | | | | encrypted password. Kerberized `login' might use this, if I get around to implementing the complete Allspice System behavior.
* BSD 4.4 Lite Usr.bin SourcesRodney W. Grimes1994-05-271-0/+231
generated by cgit v1.2.3-56-ge451 (git 2.39.0) at 2024-05-18 10:37:35 +0000