.\" Copyright (c) 1988, 1991 The Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)passwd.5 6.7 (Berkeley) 4/29/91
.Nd format of the password file
files are files consisting of newline separated records, one per user,
containing ten colon (``:'') separated fields. These fields are as
.Bl -tag -width password -offset indent
User's general classification (unused).
General information about the user.
field is the login used to access the computer account, and the
field is the number associated with it. They should both be unique
across the system (and often across a group of systems) since they
While it is possible to have multiple entries with identical login names
and/or identical user id's, it is usually a mistake to do so. Routines
that manipulate these files will often return only one of the multiple
entries, and that one by random selection.
The login name must never begin with a hyphen (``-''); also, it is strongly
suggested that neither upper-case characters or dots (``.'') be part
of the name, as this tends to confuse mailers. No field may contain a
colon (``:'') as this has been used historically to separate the fields
The password field is the
field is empty, no password will be required to gain access to the
machine. This is almost invariably a mistake.
Because these files contain the encrypted user passwords, they should
not be readable by anyone without appropriate privileges.
The group field is the group that the user will be placed in upon login.
Since this system supports multiple groups (see
this field currently has little special meaning.
field is currently unused. In the near future it will be a key to
style database of user attributes.
field is the number in seconds,
from the epoch, until the
password for the account must be changed.
This field may be left empty to turn off the password aging feature.
field is the number in seconds,
from the epoch, until the
This field may be left empty to turn off the account aging feature.
field normally contains comma (``,'') separated subfields as follows:
.Bd -unfilled -offset indent
office user's office number
wphone user's work phone number
hphone user's home phone number
This information is used by the
The user's home directory is the full
The shell field is the command interpreter the user prefers.
If there is nothing in the
User information should (and eventually will) be stored elsewhere.