File: shadow.5.xml

package info (click to toggle)
shadow 1%3A4.19.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 67,276 kB
  • sloc: sh: 44,701; ansic: 34,184; xml: 12,350; exp: 3,691; makefile: 1,656; python: 1,409; perl: 120; sed: 16
file content (286 lines) | stat: -rw-r--r-- 8,733 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
<?xml version="1.0" encoding="UTF-8"?>
<!--
   SPDX-FileCopyrightText: 1989 - 1990, Julianne Frances Haugh
   SPDX-FileCopyrightText: 2007 - 2009, Nicolas François
   SPDX-License-Identifier: BSD-3-Clause
-->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!-- SHADOW-CONFIG-HERE -->
]>
<refentry id='shadow.5'>
  <!-- $Id$ -->
  <refentryinfo>
    <author>
      <firstname>Julianne Frances</firstname>
      <surname>Haugh</surname>
      <contrib>Creation, 1989</contrib>
    </author>
    <author>
      <firstname>Thomas</firstname>
      <surname>Kłoczko</surname>
      <email>kloczek@pld.org.pl</email>
      <contrib>shadow-utils maintainer, 2000 - 2007</contrib>
    </author>
    <author>
      <firstname>Nicolas</firstname>
      <surname>François</surname>
      <email>nicolas.francois@centraliens.net</email>
      <contrib>shadow-utils maintainer, 2007 - now</contrib>
    </author>
  </refentryinfo>
  <refmeta>
    <refentrytitle>shadow</refentrytitle>
    <manvolnum>5</manvolnum>
    <refmiscinfo class="sectdesc">File Formats and Configuration Files</refmiscinfo>
    <refmiscinfo class="source">shadow-utils</refmiscinfo>
    <refmiscinfo class="version">&SHADOW_UTILS_VERSION;</refmiscinfo>
  </refmeta>
  <refnamediv id='name'>
    <refname>shadow</refname>
    <refpurpose>shadowed password file</refpurpose>
  </refnamediv>

  <refsect1 id='description'>
    <title>DESCRIPTION</title>
    <para>
      <filename>shadow</filename> is a file which contains the password
      information for the system's accounts and optional aging
      information.
    </para>

    <para>
      This file must not be readable by regular users if password security
      is to be maintained.
    </para>

    <para>
      Each line of this file contains 9 fields, separated by colons
      (<quote>:</quote>), in the following order:
    </para>

    <variablelist>
      <varlistentry>
	<term><emphasis role="bold">login name</emphasis></term>
	<listitem>
	  <para>
	    It must be a valid account name, which exists on the system.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><emphasis role="bold">encrypted password</emphasis></term>
	<listitem>
	  <para>
	    If the password field is empty, the user can log in without a password.
	    However, some applications that read
	    the <filename>/etc/shadow</filename> file
	    might block access
	    if the password field is empty.
	  </para>
	  <para>
	    If the password field begins with an exclamation mark <emphasis>!</emphasis>,
	    the password is locked.
	    The remaining characters on the
	    line represent the password field before the password was
	    locked.
	  </para>
	  <para>
	    Refer to <citerefentry><refentrytitle>crypt</refentrytitle>
	    <manvolnum>3</manvolnum></citerefentry> for details on how
	    this string is interpreted.
	  </para>
	  <para>
	    If the password field contains a string that is not a valid
	    result of <citerefentry><refentrytitle>crypt</refentrytitle>
	    <manvolnum>3</manvolnum></citerefentry>, for instance ! or *,
	    the user cannot use a UNIX password to log in.
	    However, the user may log in the system by other means.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>
	  <emphasis role="bold">date of last password change</emphasis>
	</term>
	<listitem>
	  <para>
	    The date of the last password change, expressed as the number
	    of days since 1970-01-01 00:00:00 UTC.
	  </para>
	  <para>
	    The value 0 indicates that the user must change their password
	    the next time they log in to the system.
	  </para>
	  <para>
	    An empty field means that password aging features are
	    disabled.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><emphasis role="bold">minimum password age</emphasis></term>
	<listitem>
	  <para>
	    The minimum password age is the number of days the user must wait
	    before they can change their password again.
	  </para>
	  <para>
	    An empty field and value 0 mean that there is no minimum
	    password age.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><emphasis role="bold">maximum password age</emphasis></term>
	<listitem>
	  <para>
	    The maximum password age is the number of days after which the
	    user must change their password.
	  </para>
	  <para>
	    After this number of days has elapsed, the password may still be valid.
	    The user is prompted to change their password at the next login.
	  </para>
	  <para>
	    An empty field means that there are no maximum password age,
	    no password warning period, and no password inactivity period
	    (see below).
	  </para>
	  <para>
	    If the maximum password age is lower than the minimum password
	    age, the user cannot change her password.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>
	  <emphasis role="bold">password warning period</emphasis>
	</term>
	<listitem>
	  <para>
	    The number of days before a password expires
	    (see the maximum password age above)
	    during which the user is warned.
	  </para>
	  <para>
	    An empty field and value 0 mean that there is no password
	    warning period.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>
	  <emphasis role="bold">password inactivity period</emphasis>
	</term>
	<listitem>
	  <para>
	    The number of days after a password expires
	    (see the maximum password age above)
	    during which the password is still accepted,
	    and the user must update their password at the next login.
	  </para>
	  <para>
	    After the password expires and the password inactivity period elapses,
	    the user cannot log in and must contact their administrator.
	  </para>
	  <para>
	    An empty string means that no inactivity period is enforced.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>
	  <emphasis role="bold">account expiration date</emphasis>
	</term>
	<listitem>
	  <para>
	    The date when the account expires,
	    expressed as the number of days since 1970-01-01.
	  </para>
	  <para>
	    Note that account expiration differs from password expiration.
	    Account expiration prevents the user from logging in,
	    whereas password expiration only prevents users from logging in
	    with their password.
	  </para>
	  <para>
	    An empty field means that the account never expires.
	  </para>
	  <para>
	    The value 0 should not be used,
	    as it is interpreted either as an account with no expiration
	    or as an expiration date of 1970-01-01.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><emphasis role="bold">reserved field</emphasis></term>
	<listitem>
	  <para>This field is reserved for future use.</para>
	</listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id='files'>
    <title>FILES</title>
    <variablelist>
      <varlistentry>
	<term><filename>/etc/passwd</filename></term>
	<listitem>
	  <para>User account information.</para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><filename>/etc/shadow</filename></term>
	<listitem>
	  <para>Secure user account information.</para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><filename>/etc/shadow-</filename></term>
	<listitem>
	  <para>Backup file for /etc/shadow.</para>
	  <para>
	    Note that this file is used by the tools of the shadow
	    toolsuite, but not by all user and password management tools.
	  </para>
	</listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id='see_also'>
    <title>SEE ALSO</title>
    <para>
      <citerefentry>
	<refentrytitle>chage</refentrytitle><manvolnum>1</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>login</refentrytitle><manvolnum>1</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>passwd</refentrytitle><manvolnum>1</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>pwck</refentrytitle><manvolnum>8</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>pwconv</refentrytitle><manvolnum>8</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>pwunconv</refentrytitle><manvolnum>8</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>su</refentrytitle><manvolnum>1</manvolnum>
      </citerefentry>,
      <citerefentry>
	<refentrytitle>sulogin</refentrytitle><manvolnum>8</manvolnum>
      </citerefentry>.
    </para>
  </refsect1>
</refentry>