IPnom Home • Manuals • FreeBSD

 FreeBSD Man Pages

Man Sections:Commands (1)System Calls (2)Library Functions (3)Device Drivers (4)File Formats (5)Miscellaneous (7)System Utilities (8)
Keyword Live Search (10 results max):
 Type in part of a command in the search box.
 
Index:
  a.out(5)
  acct(5)
  adduser.conf(5)
  aliases(5)
  amd.conf(5)
  auth.conf(5)
  big5(5)
  bluetooth.hosts(5)
  bluetooth.protocols(5)
  bootparams(5)
  bootptab(5)
  config(5)
  core(5)
  crontab(5)
  ctm(5)
  cvs(5)
  devd.conf(5)
  devfs(5)
  device.hints(5)
  dhclient.conf(5)
  dhclient.leases(5)
  dhcp-eval(5)
  dhcp-options(5)
  dir(5)
  dirent(5)
  disktab(5)
  editrc(5)
  elf(5)
  ethers(5)
  euc(5)
  eui64(5)
  exports(5)
  fbtab(5)
  fdescfs(5)
  finger.conf(5)
  forward(5)
  fs(5)
  fstab(5)
  ftpchroot(5)
  gb18030(5)
  gb2312(5)
  gbk(5)
  gettytab(5)
  groff_font(5)
  groff_out(5)
  groff_tmac(5)
  group(5)
  hcsecd.conf(5)
  hesiod.conf(5)
  hosts(5)
  hosts.equiv(5)
  hosts.lpd(5)
  hosts_access(5)
  hosts_options(5)
  inetd.conf(5)
  info(5)
  inode(5)
  intro(5)
  ipf(5)
  ipnat(5)
  ipnat.conf(5)
  ipsend(5)
  isdnd.acct(5)
  isdnd.rates(5)
  isdnd.rc(5)
  kbdmap(5)
  keycap(5)
  keymap(5)
  krb5.conf(5)
  lastlog(5)
  libarchive-formats(5)
  libmap.conf(5)
  link(5)
  linprocfs(5)
  loader.conf(5)
  login.access(5)
  login.conf(5)
  mac.conf(5)
  magic(5)
  mailer.conf(5)
  make.conf(5)
  malloc.conf(5)
  master.passwd(5)
  moduli(5)
  motd(5)
  msdos(5)
  msdosfs(5)
  mskanji(5)
  named.conf(5)
  netconfig(5)
  netgroup(5)
  netid(5)
  networks(5)
  newsyslog.conf(5)
  nologin(5)
  nsmb.conf(5)
  nsswitch.conf(5)
  ntp.conf(5)
  ntp.keys(5)
  opieaccess(5)
  opiekeys(5)
  passwd(5)
  pbm(5)
  pccard.conf(5)
  periodic.conf(5)
  pf.conf(5)
  pf.os(5)
  phones(5)
  printcap(5)
  procfs(5)
  protocols(5)
  publickey(5)
  pw.conf(5)
  quota.group(5)
  quota.user(5)
  radius.conf(5)
  rc.conf(5)
  rcsfile(5)
  remote(5)
  resolv.conf(5)
  resolver(5)
  rhosts(5)
  rndc.conf(5)
  rpc(5)
  rrenumd.conf(5)
  rtadvd.conf(5)
  services(5)
  shells(5)
  ssh_config(5)
  sshd_config(5)
  stab(5)
  style.Makefile(5)
  sysctl.conf(5)
  syslog.conf(5)
  tacplus.conf(5)
  tar(5)
  term(5)
  termcap(5)
  terminfo(5)
  texinfo(5)
  tmac(5)
  ttys(5)
  tzfile(5)
  usbd.conf(5)
  utf2(5)
  utf8(5)
  utmp(5)
  uuencode(5)
  uuencode.format(5)
  vgrindefs(5)
  wtmp(5)

master.passwd(5)

NAME

     passwd, master.passwd -- format of the password file


DESCRIPTION

     The passwd files are the local source of password information.  They can
     be used in conjunction with the Hesiod domains `passwd' and `uid', and
     the NIS maps `passwd.byname', `passwd.byuid', `master.passwd.byname', and
     `master.passwd.byuid', as controlled by nsswitch.conf(5).

     For consistency, none of these files should ever be modified manually.

     The master.passwd file is readable only by root, and consists of newline
     separated records, one per user, containing ten colon (``:'') separated
     fields.  These fields are as follows:

	   name      User's login name.

	   password  User's encrypted password.

	   uid	     User's id.

	   gid	     User's login group id.

	   class     User's login class.

	   change    Password change time.

	   expire    Account expiration time.

	   gecos     General information about the user.

	   home_dir  User's home directory.

	   shell     User's login shell.

     The passwd file is generated from the master.passwd file by pwd_mkdb(8),
     has the class, change, and expire fields removed, and the password field
     replaced by a ``*''.

     The name field is the login used to access the computer account, and the
     uid field is the number associated with it.  They should both be unique
     across the system (and often across a group of systems) since they con-
     trol file access.

     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
     in the user database.

     The password field is the encrypted form of the password, see crypt(3).
     If the password field is empty, no password will be required to gain
     The class field is a key for a user's login class.  Login classes are
     defined in login.conf(5), which is a termcap(5) style database of user
     attributes, accounting, resource, and environment settings.

     The change field is the number of seconds from the epoch, UTC, until the
     password for the account must be changed.	This field may be left empty
     to turn off the password aging feature.

     The expire field is the number of seconds from the epoch, UTC, until the
     account expires.  This field may be left empty to turn off the account
     aging feature.

     The gecos field normally contains comma (``,'') separated subfields as
     follows:

	   name    user's full name
	   office  user's office number
	   wphone  user's work phone number
	   hphone  user's home phone number

     The full name may contain a ampersand (``&'') which will be replaced by
     the capitalized login name when the gecos field is displayed or used by
     various programs such as finger(1), sendmail(8), etc.

     The office and phone number subfields are used by the finger(1) program,
     and possibly other applications.

     The user's home directory is the full UNIX path name where the user will
     be placed on login.

     The shell field is the command interpreter the user prefers.  If there is
     nothing in the shell field, the Bourne shell (/bin/sh) is assumed.


HESIOD SUPPORT

     If `dns' is specified for the `passwd' database in nsswitch.conf(5), then
     passwd lookups occur from the `passwd' Hesiod domain.


NIS SUPPORT

     If `nis' is specified for the `passwd' database in nsswitch.conf(5), then
     passwd lookups occur from the `passwd.byname', `passwd.byuid',
     `master.passwd.byname', and `master.passwd.byuid' NIS maps.


COMPAT SUPPORT

     If `compat' is specified for the `passwd' database, and either `dns' or
     `nis' is specified for the `passwd_compat' database in nsswitch.conf(5),
     then the passwd file also supports standard `+/-' exclusions and inclu-
     sions, based on user names and netgroups.

     Lines beginning with a ``-'' (minus sign) are entries marked as being
     excluded from any following inclusions, which are marked with a ``+''
     (plus sign).

     If the second character of the line is a ``@'' (at sign), the operation
     involves the user fields of all entries in the netgroup specified by the
     remaining characters of the name field.  Otherwise, the remainder of the
     name field is assumed to be a specific user name.

     The ``+'' token may also be alone in the name field, which causes all
     the passwd field may also be overridden.


FILES

     /etc/passwd	 ASCII password file, with passwords removed
     /etc/pwd.db	 db(3)-format password database, with passwords
			 removed
     /etc/master.passwd  ASCII password file, with passwords intact
     /etc/spwd.db	 db(3)-format password database, with passwords intact


SEE ALSO

     chpass(1), login(1), passwd(1), crypt(3), getpwent(3), login.conf(5),
     netgroup(5), adduser(8), pw(8), pwd_mkdb(8), vipw(8), yp(8)

     Managing NFS and NIS (O'Reilly & Associates)


BUGS

     User information should (and eventually will) be stored elsewhere.

     Placing `compat' exclusions in the file after any inclusions will have
     unexpected results.


COMPATIBILITY

     The password file format has changed since 4.3BSD.  The following awk
     script can be used to convert your old-style password file into a new
     style password file.  The additional fields ``class'', ``change'' and
     ``expire'' are added, but are turned off by default.  Class is currently
     not implemented, but change and expire are; to set them, use the current
     day in seconds from the epoch + whatever number of seconds of offset you
     want.

	   BEGIN { FS = ":"}
	   { print $1 ":" $2 ":" $3 ":" $4 "::0:0:" $5 ":" $6 ":" $7 }


HISTORY

     A passwd file format appeared in Version 6 AT&T UNIX.

     The NIS passwd file format first appeared in SunOS.

     The Hesiod support first appeared in FreeBSD 4.1.	It was imported from
     the NetBSD Project, where it first appeared in NetBSD 1.4.

FreeBSD 5.4		       February 7, 2005 		   FreeBSD 5.4

SPONSORED LINKS




Man(1) output converted with man2html , sed , awk