1.\" Copyright (c) 1995-1996 Wolfram Schneider <wosch@FreeBSD.org>. Berlin. 2.\" All rights reserved. 3.\" Copyright (c) 2002-2004 Michael Telahun Makonnen <mtm@FreeBSD.org> 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 15.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND 16.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 17.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 18.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 19.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 20.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 21.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 22.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 23.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 24.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 25.\" SUCH DAMAGE. 26.\" 27.\" $FreeBSD: src/usr.sbin/adduser/adduser.8,v 1.62 2008/03/16 21:36:05 brueffer Exp $ 28.\" 29.Dd October 31, 2011 30.Dt ADDUSER 8 31.Os 32.Sh NAME 33.Nm adduser 34.Nd command for adding new users 35.Sh SYNOPSIS 36.Nm 37.Op Fl CDENShq 38.Op Fl G Ar groups 39.Op Fl L Ar login_class 40.Op Fl M Ar mode 41.Op Fl d Ar partition 42.Op Fl f Ar file 43.Op Fl g Ar login_group 44.Op Fl k Ar dotdir 45.Op Fl m Ar message_file 46.Op Fl s Ar shell 47.Op Fl u Ar uid_start 48.Op Fl w Ar type 49.Sh DESCRIPTION 50The 51.Nm 52utility is a shell script, implemented around the 53.Xr pw 8 54command, for adding new users. 55It creates passwd/group entries, a home directory, 56copies dotfiles and sends the new user a welcome message. 57It supports two modes of operation. 58It may be used interactively 59at the command line to add one user at a time, or it may be directed 60to get the list of new users from a file and operate in batch mode 61without requiring any user interaction. 62.Sh RESTRICTIONS 63.Bl -tag -width indent 64.It username 65Login name. 66The user name is restricted to whatever 67.Xr pw 8 68will accept. 69Generally this means it 70may contain only lowercase characters or digits but cannot begin with the 71.Ql - 72character. 73Maximum length 74is 16 characters. 75The reasons for this limit are historical. 76Given that people have traditionally wanted to break this 77limit for aesthetic reasons, it has never been of great importance to break 78such a basic fundamental parameter in 79.Ux . 80You can change 81.Dv UT_NAMESIZE 82in 83.In utmp.h 84and recompile the 85world; people have done this and it works, but you will have problems 86with any precompiled programs, or source that assumes the 8-character 87name limit, such as NIS. 88The NIS protocol mandates an 8-character username. 89If you need a longer login name for e-mail addresses, 90you can define an alias in 91.Pa /etc/mail/aliases . 92.It "full name" 93This is typically known as the gecos field and usually contains 94the user's full name. 95Additionally, it may contain a comma separated 96list of values such as office number and work and home phones. 97If the 98name contains an ampersand it will be replaced by the capitalized 99login name when displayed by other programs. 100The 101.Ql \&: 102character is not allowed. 103.It shell 104Unless the 105.Fl S 106argument is supplied only valid shells from the shell database 107.Pq Pa /etc/shells 108are allowed. 109In addition, 110either the base name or the full path of the shell may be supplied. 111.It UID 112Automatically generated or your choice. 113It must be less than 32000. 114.It "GID/login group" 115Automatically generated or your choice. 116It must be less than 32000. 117.It password 118You may choose an empty password, disable the password, use a 119randomly generated password or specify your own plaintext password, 120which will be encrypted before being stored in the user database. 121.El 122.Sh UNIQUE GROUPS 123Perhaps you are missing what 124.Em can 125be done with this scheme that falls apart 126with most other schemes. 127With each user in their own group, 128they can safely run with a umask of 002 instead of the usual 022 129and create files in their home directory 130without worrying about others being able to change them. 131.Pp 132For a shared area you create a separate UID/GID (like cvs or ncvs on freefall), 133you place each person that should be able to access this area into that new 134group. 135.Pp 136This model of UID/GID administration allows far greater flexibility than lumping 137users into groups and having to muck with the umask when working in a shared 138area. 139.Pp 140I have been using this model for almost 10 years and found that it works 141for most situations, and has never gotten in the way. 142(Rod Grimes) 143.Sh CONFIGURATION 144The 145.Nm 146utility reads its configuration information from 147.Pa /etc/adduser.conf . 148If this file does not exist, it will use predefined defaults. 149While this file may be edited by hand, 150the safer option is to use the 151.Fl C 152command line argument. 153With this argument, 154.Nm 155will start interactive input, save the answers to its prompts in 156.Pa /etc/adduser.conf , 157and promptly exit without modifying the user 158database. 159Options specified on the command line will take precedence over 160any values saved in this file. 161.Sh OPTIONS 162.Bl -tag -width indent 163.It Fl C 164Create new configuration file and exit. 165This option is mutually exclusive with the 166.Fl f 167option. 168.It Fl d Ar partition 169Home partition. 170Default partition, under which all user directories 171will be located. 172The 173.Pa /nonexistent 174partition is considered special. 175The 176.Nm 177script will not create and populate a home directory by that name. 178Otherwise, 179by default it attempts to create a home directory. 180.It Fl D 181Do not attempt to create the home directory. 182.It Fl E 183Disable the account. 184This option will lock the account by prepending the string 185.Dq Li *LOCKED* 186to the password field. 187The account may be unlocked 188by the super-user with the 189.Xr pw 8 190command: 191.Pp 192.D1 Nm pw Cm unlock Op Ar name | uid 193.It Fl f Ar file 194Get the list of accounts to create from 195.Ar file . 196If 197.Ar file 198is 199.Dq Fl , 200then get the list from standard input. 201If this option is specified, 202.Nm 203will operate in batch mode and will not seek any user input. 204If an error is encountered while processing an account, it will write a 205message to standard error and move to the next account. 206The format 207of the input file is described below. 208.It Fl g Ar login_group 209Normally, 210if no login group is specified, 211it is assumed to be the same as the username. 212This option makes 213.Ar login_group 214the default. 215.It Fl G Ar groups 216Space-separated list of additional groups. 217This option allows the user to specify additional groups to add users to. 218The user is a member of these groups in addition to their login group. 219.It Fl h 220Print a summary of options and exit. 221.It Fl k Ar directory 222Copy files from 223.Ar directory 224into the home 225directory of new users; 226.Pa dot.foo 227will be renamed to 228.Pa .foo . 229.It Fl L Ar login_class 230Set default login class. 231.It Fl m Ar file 232Send new users a welcome message from 233.Ar file . 234Specifying a value of 235.Cm no 236for 237.Ar file 238causes no message to be sent to new users. 239Please note that the message 240file can reference the internal variables of the 241.Nm 242script. 243.It Fl M Ar mode 244Create the home directory with permissions set to 245.Ar mode . 246.It Fl N 247Do not read the default configuration file. 248.It Fl q 249Minimal user feedback. 250In particular, the random password will not be echoed to 251standard output. 252.It Fl s Ar shell 253Default shell for new users. 254The 255.Ar shell 256argument may be the base name of the shell or the full path. 257Unless the 258.Fl S 259argument is supplied the shell must exist in 260.Pa /etc/shells 261or be the special shell 262.Em nologin 263to be considered a valid shell. 264.It Fl S 265The existence or validity of the specified shell will not be checked. 266.It Fl u Ar uid 267Use UIDs from 268.Ar uid 269on up. 270.It Fl w Ar type 271Password type. 272The 273.Nm 274utility allows the user to specify what type of password to create. 275The 276.Ar type 277argument may have one of the following values: 278.Bl -tag -width ".Cm random" 279.It Cm no 280Disable the password. 281Instead of an encrypted string, the password field will contain a single 282.Ql * 283character. 284The user may not log in until the super-user 285manually enables the password. 286.It Cm none 287Use an empty string as the password. 288.It Cm yes 289Use a user-supplied string as the password. 290In interactive mode, 291the user will be prompted for the password. 292In batch mode, the 293last (10th) field in the line is assumed to be the password. 294.It Cm random 295Generate a random string and use it as a password. 296The password will be echoed to standard output. 297In addition, it will be available for inclusion in the message file in the 298.Va randompass 299variable. 300.El 301.El 302.Sh FORMAT 303When the 304.Fl f 305option is used, the account information must be stored in a specific 306format. 307All empty lines or lines beginning with a 308.Ql # 309will be ignored. 310All other lines must contain ten colon 311.Pq Ql \&: 312separated fields as described below. 313Command line options do not take precedence 314over values in the fields. 315Only the password field may contain a 316.Ql \&: 317character as part of the string. 318.Pp 319.Sm off 320.D1 Ar name : uid : gid : class : change : expire : gecos : home_dir : shell : password 321.Sm on 322.Bl -tag -width ".Ar password" 323.It Ar name 324Login name. 325This field may not be empty. 326.It Ar uid 327Numeric login user ID. 328If this field is left empty, it will be automatically generated. 329.It Ar gid 330Numeric primary group ID. 331If this field is left empty, a group with the 332same name as the user name will be created and its GID will be used 333instead. 334.It Ar class 335Login class. 336This field may be left empty. 337.It Ar change 338Password ageing. 339This field denotes the password change date for the account. 340The format of this field is the same as the format of the 341.Fl p 342argument to 343.Xr pw 8 . 344It may be 345.Ar dd Ns - Ns Ar mmm Ns - Ns Ar yy Ns Op Ar yy , 346where 347.Ar dd 348is for the day, 349.Ar mmm 350is for the month in numeric or alphabetical format: 351.Dq Li 10 352or 353.Dq Li Oct , 354and 355.Ar yy Ns Op Ar yy 356is the four or two digit year. 357To denote a time relative to the current date the format is: 358.No + Ns Ar n Ns Op Ar mhdwoy , 359where 360.Ar n 361denotes a number, followed by the minutes, hours, days, weeks, 362months or years after which the password must be changed. 363This field may be left empty to turn it off. 364.It Ar expire 365Account expiration. 366This field denotes the expiry date of the account. 367The account may not be used after the specified date. 368The format of this field is the same as that for password ageing. 369This field may be left empty to turn it off. 370.It Ar gecos 371Full name and other extra information about the user. 372.It Ar home_dir 373Home directory. 374If this field is left empty, it will be automatically 375created by appending the username to the home partition. 376The 377.Pa /nonexistent 378home directory is considered special and 379is understood to mean that no home directory is to be 380created for the user. 381.It Ar shell 382Login shell. 383This field should contain either the base name or 384the full path to a valid login shell. 385.It Ar password 386User password. 387This field should contain a plaintext string, which will 388be encrypted before being placed in the user database. 389If the password type is 390.Cm yes 391and this field is empty, it is assumed the account will have an empty password. 392If the password type is 393.Cm random 394and this field is 395.Em not 396empty, its contents will be used 397as a password. 398This field will be ignored if the 399.Fl w 400option is used with a 401.Cm no 402or 403.Cm none 404argument. 405Be careful not to terminate this field with a closing 406.Ql \&: 407because it will be treated as part of the password. 408.El 409.Sh FILES 410.Bl -tag -width ".Pa /etc/adduser.message" -compact 411.It Pa /etc/master.passwd 412user database 413.It Pa /etc/group 414group database 415.It Pa /etc/shells 416shell database 417.It Pa /etc/login.conf 418login classes database 419.It Pa /etc/adduser.conf 420configuration file for 421.Nm 422.It Pa /etc/adduser.message 423message file for 424.Nm 425.It Pa /usr/share/skel 426skeletal login directory 427.It Pa /var/log/adduser 428logfile for 429.Nm 430.El 431.Sh SEE ALSO 432.Xr chpass 1 , 433.Xr passwd 1 , 434.Xr adduser.conf 5 , 435.Xr aliases 5 , 436.Xr group 5 , 437.Xr login.conf 5 , 438.Xr passwd 5 , 439.Xr shells 5 , 440.Xr pw 8 , 441.Xr pwd_mkdb 8 , 442.Xr rmuser 8 , 443.Xr vipw 8 , 444.Xr yp 8 445.Sh HISTORY 446The 447.Nm 448command appeared in 449.Fx 2.1 . 450.Sh AUTHORS 451.An -nosplit 452This manual page and the original script, in Perl, were written by 453.An Wolfram Schneider Aq Mt wosch@FreeBSD.org . 454The replacement script, written as a Bourne 455shell script with some enhancements, and the man page modification that 456came with it were done by 457.An Mike Makonnen Aq Mt mtm@identd.net . 458.Sh BUGS 459In order for 460.Nm 461to correctly expand variables such as 462.Va $username 463and 464.Va $randompass 465in the message sent to new users, it must let the shell evaluate 466each line of the message file. 467This means that shell commands can also be embedded in the message file. 468The 469.Nm 470utility attempts to mitigate the possibility of an attacker using this 471feature by refusing to evaluate the file if it is not owned and writable 472only by the root user. 473In addition, shell special characters and operators will have to be 474escaped when used in the message file. 475.Pp 476Also, password ageing and account expiry times are currently settable 477only in batch mode or when specified in 478.Pa /etc/adduser.conf . 479The user should be able to set them in interactive mode as well. 480