1 '\" te
2 .\" Copyright 1989 AT&T Copyright (c) 2002, Sun Microsystems, Inc. All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH SHADOW 4 "Sep 15, 2005"
7 .SH NAME
8 shadow \- shadow password file
9 .SH DESCRIPTION
10 .sp
11 .LP
12 \fB/etc/shadow\fR is an access-restricted ASCII system file that stores users'
13 encrypted passwords and related information. The shadow file can be used in
14 conjunction with other shadow sources, including the \fBNIS\fR maps
15 \fBpasswd.byname\fR and \fBpasswd.byuid\fR and the NIS+ table \fBpasswd\fR.
16 Programs use the \fBgetspnam\fR(3C) routines to access this information.
17 .sp
18 .LP
19 The fields for each user entry are separated by colons. Each user is separated
20 from the next by a newline. Unlike the \fB/etc/passwd\fR file,
21 \fB/etc/shadow\fR does not have general read permission.
22 .sp
23 .LP
24 Each entry in the shadow file has the form:
25 .sp
26 .in +2
27 .nf
28 \fIusername\fR:\fIpassword\fR:\fIlastchg\fR:\fImin\fR:\fImax\fR:\fIwarn\fR:\fIinactive\fR:\fIexpire\fR:\fIflag\fR
29 .fi
30 .in -2
133 aging.
134 .sp
135 .LP
136 The encrypted password consists of at most \fBCRYPT_MAXCIPHERTEXTLEN\fR
137 characters chosen from a 64-character alphabet (\fB\&.\fR, \fB/\fR,
138 \fB0\(mi9\fR, \fBA\(miZ\fR, \fBa\(miz\fR). Two additional special characters,
139 "$" and ",", can also be used and are defined in \fBcrypt\fR(3C). To update
140 this file, use the \fBpasswd\fR(1), \fBuseradd\fR(1M), \fBusermod\fR(1M), or
141 \fBuserdel\fR(1M) commands.
142 .sp
143 .LP
144 In order to make system administration manageable, \fB/etc/shadow\fR entries
145 should appear in exactly the same order as \fB/etc/passwd\fR entries; this
146 includes ``+'' and ``-'' entries if the \fBcompat\fR source is being used (see
147 \fBnsswitch.conf\fR(4)).
148 .sp
149 .LP
150 Values for the various time-related fields are interpreted as Greenwich Mean
151 Time.
152 .SH FILES
153 .sp
154 .ne 2
155 .na
156 \fB\fB/etc/shadow\fR\fR
157 .ad
158 .RS 22n
159 shadow password file
160 .RE
161
162 .sp
163 .ne 2
164 .na
165 \fB\fB/etc/passwd\fR\fR
166 .ad
167 .RS 22n
168 password file
169 .RE
170
171 .sp
172 .ne 2
173 .na
174 \fB\fB/etc/nsswitch.conf\fR\fR
175 .ad
176 .RS 22n
177 name-service switch configuration file
178 .RE
179
180 .sp
181 .ne 2
182 .na
183 \fB\fB/var/adm/lastlog\fR\fR
184 .ad
185 .RS 22n
186 time of last login
187 .RE
188
189 .SH ATTRIBUTES
190 .sp
191 .LP
192 See \fBattributes\fR(5) for descriptions of the following attributes:
193 .sp
194
195 .sp
196 .TS
197 box;
198 c | c
199 l | l .
200 ATTRIBUTE TYPE ATTRIBUTE VALUE
201 _
202 Interface Stability Stable
203 .TE
204
205 .SH SEE ALSO
206 .sp
207 .LP
208 \fBlogin\fR(1), \fBpasswd\fR(1), \fBuseradd\fR(1M), \fBuserdel\fR(1M),
209 \fBusermod\fR(1M), \fBstrtol\fR(3C), \fBcrypt\fR(3C), \fBcrypt_gensalt\fR(3C),
210 \fBgetspnam\fR(3C), \fBputspent\fR(3C), \fBnsswitch.conf\fR(4),
211 \fBpasswd\fR(4), \fBattributes\fR(5), \fBpam_unix_account\fR(5),
212 \fBpam_unix_auth\fR(5)
213 .SH NOTES
214 .sp
215 .LP
216 If password aging is turned on in any name service the \fIpasswd:\fR line in
217 the \fB/etc/nsswitch.conf\fR file must have a format specified in the
218 \fBnsswitch.conf\fR(4) man page.
219 .sp
220 .LP
221 If the \fB/etc/nsswitch.conf\fR passwd policy is not in one of the supported
222 formats, logins will not be allowed upon password expiration, because the
223 software does not know how to handle password updates under these conditions.
224 See \fBnsswitch.conf\fR(4) for additional information.
|
1 '\" te
2 .\" Copyright 1989 AT&T Copyright (c) 2002, Sun Microsystems, Inc. All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH SHADOW 4 "Nov 9, 2015"
7 .SH NAME
8 shadow \- shadow password file
9 .SH DESCRIPTION
10 .LP
11 \fB/etc/shadow\fR is an access-restricted ASCII system file that stores users'
12 encrypted passwords and related information. The shadow file can be used in
13 conjunction with other shadow sources, including the \fBNIS\fR maps
14 \fBpasswd.byname\fR and \fBpasswd.byuid\fR and the NIS+ table \fBpasswd\fR.
15 Programs use the \fBgetspnam\fR(3C) routines to access this information.
16 .sp
17 .LP
18 The fields for each user entry are separated by colons. Each user is separated
19 from the next by a newline. Unlike the \fB/etc/passwd\fR file,
20 \fB/etc/shadow\fR does not have general read permission.
21 .sp
22 .LP
23 Each entry in the shadow file has the form:
24 .sp
25 .in +2
26 .nf
27 \fIusername\fR:\fIpassword\fR:\fIlastchg\fR:\fImin\fR:\fImax\fR:\fIwarn\fR:\fIinactive\fR:\fIexpire\fR:\fIflag\fR
28 .fi
29 .in -2
132 aging.
133 .sp
134 .LP
135 The encrypted password consists of at most \fBCRYPT_MAXCIPHERTEXTLEN\fR
136 characters chosen from a 64-character alphabet (\fB\&.\fR, \fB/\fR,
137 \fB0\(mi9\fR, \fBA\(miZ\fR, \fBa\(miz\fR). Two additional special characters,
138 "$" and ",", can also be used and are defined in \fBcrypt\fR(3C). To update
139 this file, use the \fBpasswd\fR(1), \fBuseradd\fR(1M), \fBusermod\fR(1M), or
140 \fBuserdel\fR(1M) commands.
141 .sp
142 .LP
143 In order to make system administration manageable, \fB/etc/shadow\fR entries
144 should appear in exactly the same order as \fB/etc/passwd\fR entries; this
145 includes ``+'' and ``-'' entries if the \fBcompat\fR source is being used (see
146 \fBnsswitch.conf\fR(4)).
147 .sp
148 .LP
149 Values for the various time-related fields are interpreted as Greenwich Mean
150 Time.
151 .SH FILES
152 .ne 2
153 .na
154 \fB\fB/etc/shadow\fR\fR
155 .ad
156 .RS 22n
157 shadow password file
158 .RE
159
160 .sp
161 .ne 2
162 .na
163 \fB\fB/etc/passwd\fR\fR
164 .ad
165 .RS 22n
166 password file
167 .RE
168
169 .sp
170 .ne 2
171 .na
172 \fB\fB/etc/nsswitch.conf\fR\fR
173 .ad
174 .RS 22n
175 name-service switch configuration file
176 .RE
177
178 .sp
179 .ne 2
180 .na
181 \fB\fB/var/adm/lastlog.v2\fR\fR
182 .ad
183 .RS 22n
184 time of last login
185 .RE
186
187 .SH ATTRIBUTES
188 .LP
189 See \fBattributes\fR(5) for descriptions of the following attributes:
190 .sp
191
192 .sp
193 .TS
194 box;
195 c | c
196 l | l .
197 ATTRIBUTE TYPE ATTRIBUTE VALUE
198 _
199 Interface Stability Stable
200 .TE
201
202 .SH SEE ALSO
203 .LP
204 \fBlogin\fR(1), \fBpasswd\fR(1), \fBuseradd\fR(1M), \fBuserdel\fR(1M),
205 \fBusermod\fR(1M), \fBstrtol\fR(3C), \fBcrypt\fR(3C), \fBcrypt_gensalt\fR(3C),
206 \fBgetspnam\fR(3C), \fBputspent\fR(3C), \fBnsswitch.conf\fR(4),
207 \fBpasswd\fR(4), \fBattributes\fR(5), \fBpam_unix_account\fR(5),
208 \fBpam_unix_auth\fR(5)
209 .SH NOTES
210 .LP
211 If password aging is turned on in any name service the \fIpasswd:\fR line in
212 the \fB/etc/nsswitch.conf\fR file must have a format specified in the
213 \fBnsswitch.conf\fR(4) man page.
214 .sp
215 .LP
216 If the \fB/etc/nsswitch.conf\fR passwd policy is not in one of the supported
217 formats, logins will not be allowed upon password expiration, because the
218 software does not know how to handle password updates under these conditions.
219 See \fBnsswitch.conf\fR(4) for additional information.
|