2 .\" David L. Nugent. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
13 .\" THIS SOFTWARE IS PROVIDED BY DAVID L. NUGENT AND CONTRIBUTORS ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL DAVID L. NUGENT OR CONTRIBUTORS BE LIABLE
17 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
25 .\" $FreeBSD: src/usr.sbin/pw/pw.conf.5,v 1.16 2007/03/30 11:23:10 le Exp $
32 .Nd format of the pw.conf configuration file
36 contains configuration data for the
41 utility is used for maintenance of the system password and group
42 files, allowing users and groups to be added, deleted and changed.
43 This file may be modified via the
49 option, or by editing it directly with a text editor.
53 is treated either a comment or as configuration data;
54 blank lines and lines commencing with a
56 character are considered comments, and any remaining lines are
57 examined for a leading keyword, followed by corresponding data.
59 Keywords recognized by
62 .Bl -tag -width password_days -offset indent -compact
64 affect passwords generated for new users
66 reuse gaps in uid sequences
68 reuse gaps in gid sequences
74 where to obtain default home contents
76 mail to send to new users
78 log user/group modifications to this file
80 root directory for home directories
82 permissions for home directory
84 paths in which to locate shell programs
86 list of valid shells (without path)
88 default shell (without path)
92 add new users to this groups
94 place new users in this login class
97 range of valid default user ids
100 range of valid default group ids
102 days after which account expires
104 days after which password expires
110 .Bl -tag -width password_days -offset indent -compact
112 disable login on newly created accounts
114 force the password to be the account name
116 force a blank password
118 generate a random password
121 The second and third options are insecure and should be avoided if
122 possible on a publicly accessible system.
123 The first option requires that the superuser run
125 to set a password before the account may be used.
126 This may also be useful for creating administrative accounts.
127 The final option causes
129 to respond by printing a randomly generated password on stdout.
130 This is the preferred and most secure option.
133 utility also provides a method of setting a specific password for the new
134 user via a filehandle (command lines are not secure).
140 determine the method by which new user and group id numbers are
144 in this field will cause
146 to search for the first unused user or group id within the allowed
149 will ensure that no other existing user or group id within the range
150 is numerically lower than the new one generated, and therefore avoids
151 reusing gaps in the user or group id sequence that are caused by
152 previous user or group deletions.
153 Note that if the default group is not specified using the
157 will create a new group for the user and attempt to keep the new
158 user's uid and gid the same.
159 If the new user's uid is currently in use as a group id, then the next
160 available group id is chosen instead.
164 servers which maintain a separate passwd database to
165 .Pa /etc/master.passwd ,
166 this option allows the additional file to be concurrently updated
167 as user records are added, modified or removed.
168 If blank or set to 'no', no additional database is updated.
169 An absolute pathname must be used.
173 keyword nominates a directory from which the contents of a user's
174 new home directory is constructed.
181 option causes the user's home directory to be created and populated
182 using the files contained in the
186 To send an initial email to new users, the
188 keyword may be used to specify a path name to a file containing
189 the message body of the message to be sent.
190 To avoid sending mail when accounts are created, leave this entry
196 option allows logging of password file modifications into the
198 To avoid creating or adding to such a logfile, then leave this
199 field blank or specify
204 keyword is mandatory.
205 This specifies the location of the directory in which all new user
206 home directories are created.
211 It specifies the creation mask of the user's home directory and is modified by
216 keyword specifies a list of directories - separated by colons
218 - which contain the programs used by the login shells.
222 keyword specifies a list of programs available for use as login
224 This list is a comma-separated list of shell names which should
226 These shells must exist in one of the directories nominated by
231 keyword nominates which shell program to use for new users when
232 none is specified on the
238 keyword defines the primary group (the group id number in the
239 password file) used for new accounts.
240 If left blank, or the word
242 is used, then each new user will have a corresponding group of
243 their own created automatically.
244 This is the recommended procedure for new users as it best secures each
245 user's files against interference by other users of the system
248 normally used by the user.
252 keyword provides an automatic means of placing new users into groups within
256 This is useful where all users share some resources, and is preferable
257 to placing users into the same primary group.
258 The effect of this keyword can be overridden using the
266 field determines the login class (See
268 that new users will be allocated unless overwritten by
276 keywords determine the allowed ranges of automatically allocated user
277 and group id numbers.
278 The default values for both user and group ids are 1000 and 32000 as
279 minimum and maximum respectively.
280 The user and group id's actually used when creating an account with
282 may be overridden using the
286 command line options.
292 are used to automatically calculate the number of days from the date
293 on which an account is created when the account will expire or the
294 user will be forced to change the account's password.
297 in either field will disable the corresponding (account or password)
300 The maximum line length of
303 Longer lines will be skipped and treated
306 .Bl -tag -width /etc/master.passwd -compact
309 .It Pa /etc/master.passwd