[unix-history] / usr / share / man / cat5 / passwd.0



PASSWD(5)		      1990			PASSWD(5)


N\bNA\bAM\bME\bE
     passwd - password files

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     _\bP_\ba_\bs_\bs_\bw_\bd files are files consisting of newline separated
     records, one per user, containing ten colon (``:'')
     separated fields.	These fields are as follows:

	   name          user's login name
	   password	 user's _\be_\bn_\bc_\br_\by_\bp_\bt_\be_\bd password
	   uid		 user's id
	   gid		 user's login group id
	   class	 user's general classification (unused)
	   change	 password change time
	   expire	 account expiration time
	   gecos	 general information about the user
	   home_dir	 user's home directory
	   shell	 user's login shell

     The _\bn_\ba_\bm_\be field is the login used to access the computer
     account, and the _\bu_\bi_\bd field is the number associated with it.
     They should both be unique across the system (and often
     across a group of systems) since they control file access.

     While it is possible to have multiple entries with identical
     login names and/or identical user id's, it is usually a mis-
     take to do so.  Routines that manipulate these files will
     often return only one of the multiple entries, and that one
     by random selection.

     The login name must never begin with a hyphen (``-''); also,
     it is strongly suggested that neither upper-case characters
     or dots (``.'') be part of the name, as this tends to con-
     fuse mailers.  No field may contain a colon (``:'') as this
     has been used historically to separate the fields in the
     user database.

     The password field is the _\be_\bn_\bc_\br_\by_\bp_\bt_\be_\bd form of the password.
     If the _\bp_\ba_\bs_\bs_\bw_\bo_\br_\bd field is empty, no password will be required
     to gain access to the machine.  This is almost invariably a
     mistake.  Because these files contain the encrypted user
     passwords, they should not be readable by anyone without
     appropriate privileges.

     The group field is the group that the user will be placed in
     upon login.  Since this system supports multiple groups (see
     _\bg_\br_\bo_\bu_\bp_\bs(1)) this field currently has little special meaning.

     The _\bc_\bl_\ba_\bs_\bs field is currently unused.  In the near future it
     will be a key to a _\bt_\be_\br_\bm_\bc_\ba_\bp(5) style database of user attri-
     butes.


Printed 7/27/90               June				1


PASSWD(5)		      1990			PASSWD(5)


     The _\bc_\bh_\ba_\bn_\bg_\be field is the number in seconds, GMT, from the
     epoch, until the password for the account must be changed.
     This field may be left empty to turn off the password aging
     feature.

     The _\be_\bx_\bp_\bi_\br_\be field is the number in seconds, GMT, from the
     epoch, until the account expires.	This field may be left
     empty to turn off the account aging feature.

     The _\bg_\be_\bc_\bo_\bs field normally contains comma (``,'') separated
     subfields as follows:

	   name          user's full name
	   office	 user's office number
	   wphone	 user's work phone number
	   hphone	 user's home phone number

     This information is used by the _\bf_\bi_\bn_\bg_\be_\br(1) program.

     The user's home directory is the full UNIX path name where
     the user will be placed on login.

     The shell field is the command interpreter the user prefers.
     If the _\bs_\bh_\be_\bl_\bl field is empty, the Bourne shell (/_\bb_\bi_\bn/_\bs_\bh) is
     assumed.

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     chpass(1), login(1), passwd(1), getpwent(3), mkpasswd(8),
     vipw(8) adduser(8)

B\bBU\bUG\bGS\bS
     User information should (and eventually will) be stored
     elsewhere.


Printed 7/27/90               June				2
Commit	Line	Data
3922de1d C	1
	2
	3
	4	PASSWD(5) 1990 PASSWD(5)
	5
	6
	7
	8	N\bNA\bAM\bME\bE
	9	passwd - password files
	10
	11	D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
	12	_\bP_\ba_\bs_\bs_\bw_\bd files are files consisting of newline separated
	13	records, one per user, containing ten colon (``:'')
	14	separated fields. These fields are as follows:
	15
	16	name user's login name
	17	password user's _\be_\bn_\bc_\br_\by_\bp_\bt_\be_\bd password
	18	uid user's id
	19	gid user's login group id
	20	class user's general classification (unused)
	21	change password change time
	22	expire account expiration time
	23	gecos general information about the user
	24	home_dir user's home directory
	25	shell user's login shell
	26
	27	The _\bn_\ba_\bm_\be field is the login used to access the computer
	28	account, and the _\bu_\bi_\bd field is the number associated with it.
	29	They should both be unique across the system (and often
	30	across a group of systems) since they control file access.
	31
	32	While it is possible to have multiple entries with identical
	33	login names and/or identical user id's, it is usually a mis-
	34	take to do so. Routines that manipulate these files will
	35	often return only one of the multiple entries, and that one
	36	by random selection.
	37
	38	The login name must never begin with a hyphen (``-''); also,
	39	it is strongly suggested that neither upper-case characters
	40	or dots (``.'') be part of the name, as this tends to con-
	41	fuse mailers. No field may contain a colon (``:'') as this
	42	has been used historically to separate the fields in the
	43	user database.
	44
	45	The password field is the _\be_\bn_\bc_\br_\by_\bp_\bt_\be_\bd form of the password.
	46	If the _\bp_\ba_\bs_\bs_\bw_\bo_\br_\bd field is empty, no password will be required
	47	to gain access to the machine. This is almost invariably a
	48	mistake. Because these files contain the encrypted user
	49	passwords, they should not be readable by anyone without
	50	appropriate privileges.
	51
	52	The group field is the group that the user will be placed in
	53	upon login. Since this system supports multiple groups (see
	54	_\bg_\br_\bo_\bu_\bp_\bs(1)) this field currently has little special meaning.
	55
	56	The _\bc_\bl_\ba_\bs_\bs field is currently unused. In the near future it
	57	will be a key to a _\bt_\be_\br_\bm_\bc_\ba_\bp(5) style database of user attri-
	58	butes.
	59
	60
	61
	62
	63	Printed 7/27/90 June 1
	64
65
66
67
68
69
70	PASSWD(5) 1990 PASSWD(5)
71
72
73
74	The _\bc_\bh_\ba_\bn_\bg_\be field is the number in seconds, GMT, from the
75	epoch, until the password for the account must be changed.
76	This field may be left empty to turn off the password aging
77	feature.
78
79	The _\be_\bx_\bp_\bi_\br_\be field is the number in seconds, GMT, from the
80	epoch, until the account expires. This field may be left
81	empty to turn off the account aging feature.
82
83	The _\bg_\be_\bc_\bo_\bs field normally contains comma (``,'') separated
84	subfields as follows:
85
86	name user's full name
87	office user's office number
88	wphone user's work phone number
89	hphone user's home phone number
90
91	This information is used by the _\bf_\bi_\bn_\bg_\be_\br(1) program.
92
93	The user's home directory is the full UNIX path name where
94	the user will be placed on login.
95
96	The shell field is the command interpreter the user prefers.
97	If the _\bs_\bh_\be_\bl_\bl field is empty, the Bourne shell (/_\bb_\bi_\bn/_\bs_\bh) is
98	assumed.
99
100	S\bSE\bEE\bE A\bAL\bLS\bSO\bO
101	chpass(1), login(1), passwd(1), getpwent(3), mkpasswd(8),
102	vipw(8) adduser(8)
103
104	B\bBU\bUG\bGS\bS
105	User information should (and eventually will) be stored
106	elsewhere.
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129	Printed 7/27/90 June 2
130
131
132