|
|
1.1 root 1: .\" Copyright (c) 1988 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)passwd.5 6.6 (Berkeley) 6/23/90
19: .\"
20: .TH PASSWD 5 "June 23, 1990"
21: .AT 3
22: .SH NAME
23: passwd \- password files
24: .SH DESCRIPTION
25: .I Passwd
26: files are files consisting of newline separated records, one per user,
27: containing ten colon (``:'') separated fields. These fields are as
28: follows:
29: .PP
30: .RS
31: name user's login name
32: password user's \fIencrypted\fP password
33: uid user's id
34: gid user's login group id
35: class user's general classification (unused)
36: change password change time
37: expire account expiration time
38: gecos general information about the user
39: home_dir user's home directory
40: shell user's login shell
41: .RE
42: .PP
43: The
44: .I name
45: field is the login used to access the computer account, and the
46: .I uid
47: field is the number associated with it. They should both be unique
48: across the system (and often across a group of systems) since they
49: control file access.
50: .PP
51: While it is possible to have multiple entries with identical login names
52: and/or identical user id's, it is usually a mistake to do so. Routines
53: that manipulate these files will often return only one of the multiple
54: entries, and that one by random selection.
55: .PP
56: The login name must never begin with a hyphen (``-''); also, it is strongly
57: suggested that neither upper-case characters or dots (``.'') be part
58: of the name, as this tends to confuse mailers. No field may contain a
59: colon (``:'') as this has been used historically to separate the fields
60: in the user database.
61: .PP
62: The password field is the
63: .I encrypted
64: form of the password.
65: If the
66: .I password
67: field is empty, no password will be required to gain access to the
68: machine. This is almost invariably a mistake.
69: Because these files contain the encrypted user passwords, they should
70: not be readable by anyone without appropriate privileges.
71: .PP
72: The group field is the group that the user will be placed in upon login.
73: Since this system supports multiple groups (see
74: .IR groups (1))
75: this field currently has little special meaning.
76: .PP
77: The
78: .I class
79: field is currently unused. In the near future it will be a key to
80: a
81: .IR termcap (5)
82: style database of user attributes.
83: .PP
84: The
85: .I change
86: field is the number in seconds, GMT, from the epoch, until the
87: password for the account must be changed.
88: This field may be left empty to turn off the password aging feature.
89: .PP
90: The
91: .I expire
92: field is the number in seconds, GMT, from the epoch, until the
93: account expires.
94: This field may be left empty to turn off the account aging feature.
95: .PP
96: The
97: .I gecos
98: field normally contains comma (``,'') separated subfields as follows:
99: .PP
100: .RS
101: name user's full name
102: office user's office number
103: wphone user's work phone number
104: hphone user's home phone number
105: .RE
106: .PP
107: This information is used by the
108: .IR finger (1)
109: program.
110: .PP
111: The user's home directory is the full UNIX path name where the user
112: will be placed on login.
113: .PP
114: The shell field is the command interpreter the user prefers.
115: If the
116: .I shell
117: field is empty, the Bourne shell (\fI/bin/sh\fP) is assumed.
118: .SH "SEE ALSO"
119: chpass(1), login(1), passwd(1), getpwent(3), mkpasswd(8), vipw(8) adduser(8)
120: .SH BUGS
121: User information should (and eventually will) be stored elsewhere.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.