]> git.saurik.com Git - apple/libc.git/blame - gen/getpwent.3
Libc-320.tar.gz
[apple/libc.git] / gen / getpwent.3
CommitLineData
5b2abdfb
A
1.\" Copyright (c) 1988, 1991, 1993
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
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.
12.\" 3. All advertising materials mentioning features or use of this software
13.\" must display the following acknowledgement:
14.\" This product includes software developed by the University of
15.\" California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" From: @(#)getpwent.3 8.2 (Berkeley) 12/11/93
33.\" $FreeBSD: src/lib/libc/gen/getpwent.3,v 1.18 2001/10/01 16:08:51 ru Exp $
34.\"
35.Dd September 20, 1994
36.Dt GETPWENT 3
37.Os
38.Sh NAME
39.Nm getpwent ,
40.Nm getpwnam ,
41.Nm getpwuid ,
42.Nm setpassent ,
43.Nm setpwent ,
44.Nm endpwent
45.Nd password database operations
46.Sh LIBRARY
47.Lb libc
48.Sh SYNOPSIS
49.In sys/types.h
50.In pwd.h
51.Ft struct passwd *
52.Fn getpwent void
53.Ft struct passwd *
54.Fn getpwnam "const char *login"
55.Ft struct passwd *
56.Fn getpwuid "uid_t uid"
57.Ft int
58.Fn setpassent "int stayopen"
9385eb3d 59.Ft int
5b2abdfb
A
60.Fn setpwent void
61.Ft void
62.Fn endpwent void
63.Sh DESCRIPTION
64These functions
65operate on the password database file
66which is described
67in
68.Xr passwd 5 .
69Each entry in the database is defined by the structure
70.Ar passwd
71found in the include
72file
73.Aq Pa pwd.h :
74.Bd -literal -offset indent
75struct passwd {
76 char *pw_name; /* user name */
77 char *pw_passwd; /* encrypted password */
78 uid_t pw_uid; /* user uid */
79 gid_t pw_gid; /* user gid */
80 time_t pw_change; /* password change time */
81 char *pw_class; /* user access class */
82 char *pw_gecos; /* Honeywell login info */
83 char *pw_dir; /* home directory */
84 char *pw_shell; /* default shell */
85 time_t pw_expire; /* account expiration */
86 int pw_fields; /* internal: fields filled in */
87};
88.Ed
89.Pp
90The functions
91.Fn getpwnam
92and
93.Fn getpwuid
94search the password database for the given login name or user uid,
95respectively, always returning the first one encountered.
96.Pp
97The
98.Fn getpwent
99function
100sequentially reads the password database and is intended for programs
101that wish to process the complete list of users.
102.Pp
103The
104.Fn setpassent
105function
106accomplishes two purposes.
107First, it causes
108.Fn getpwent
109to ``rewind'' to the beginning of the database.
110Additionally, if
111.Fa stayopen
112is non-zero, file descriptors are left open, significantly speeding
113up subsequent accesses for all of the routines.
114(This latter functionality is unnecessary for
115.Fn getpwent
116as it doesn't close its file descriptors by default.)
117.Pp
118It is dangerous for long-running programs to keep the file descriptors
119open as the database will become out of date if it is updated while the
120program is running.
121.Pp
122The
123.Fn setpwent
124function
125is identical to
126.Fn setpassent
127with an argument of zero.
128.Pp
129The
130.Fn endpwent
131function
132closes any open files.
133.Pp
9385eb3d
A
134As of Mac OS X 10.3, there are now different per-user behaviours of
135this function, based on the AuthenticationAuthority value
136stored for the queried user in DirectoryServices.
137.Pp
138If the queried user is still a legacy crypt password user or now
139has an AuthenticationAuthority value containing ``;basic;'',
140these routines will behave in their standard BSD fashion.
141These functions will ``shadow'' the password file, e.g.\&
5b2abdfb
A
142allow only certain programs to have access to the encrypted password.
143If the process which calls them has an effective uid of 0, the encrypted
144password will be returned, otherwise, the password field of the returned
145structure will point to the string
146.Ql * .
9385eb3d
A
147.Pp
148By default in Mac OS X 10.3 and later all users will have an
149AuthenticationAuthority will contiain the value ``;ShadowHash;''.
150These users will have a visible password value of ``********''.
151These functions
152will have no access to the encrypted password whatsoever.
153Setting or changing
154an user password must be done entirely through the DirectoryService APIs
155for this default user.
156.Pp
157There also exists an ``Apple Password Server'' user whose password
158value is also ``********'' and with an AuthenticationAuthority that
159contains the value ";ApplePasswordServer;" among other data.
160There is no getpwnam access to the password for this user either
161and again set/change password can be done through the DirectoryService API.
162.Pp
163Finally in support of local user caching there is a local cached user
164whose password is also ``********'' and has an AuthenticationAuthority
165value containing ``;LocalCachedUser;'' among other data.
166These functions also provide no access to the password for this user
167and set/change password functionality is through the DirectoryService API.
168.Pp
5b2abdfb
A
169.Sh RETURN VALUES
170The functions
171.Fn getpwent ,
172.Fn getpwnam ,
173and
174.Fn getpwuid ,
175return a valid pointer to a passwd structure on success
176and a null pointer if end-of-file is reached or an error occurs.
177The
178.Fn setpassent
9385eb3d
A
179and
180.Fn setpwent
181functions return 0 on failure and 1 on success.
5b2abdfb
A
182The
183.Fn endpwent
9385eb3d
A
184function
185has no return value.
5b2abdfb
A
186.Sh FILES
187.Bl -tag -width /etc/master.passwd -compact
188.It Pa /etc/pwd.db
189The insecure password database file
190.It Pa /etc/spwd.db
191The secure password database file
192.It Pa /etc/master.passwd
193The current password file
194.It Pa /etc/passwd
195A Version 7 format password file
196.El
197.Sh SEE ALSO
198.Xr getlogin 2 ,
199.Xr getgrent 3 ,
200.Xr yp 4 ,
5b2abdfb
A
201.Xr passwd 5 ,
202.Xr pwd_mkdb 8 ,
203.Xr vipw 8
204.Sh HISTORY
205The
206.Fn getpwent ,
207.Fn getpwnam ,
208.Fn getpwuid ,
209.Fn setpwent ,
210and
211.Fn endpwent
212functions appeared in
213.At v7 .
214The
215.Fn setpassent
216function appeared in
217.Bx 4.3 Reno .
218.Sh COMPATIBILITY
219The historic function
220.Xr setpwfile 3 ,
221which allowed the specification of alternate password databases,
222has been deprecated and is no longer available.
223.Sh BUGS
224The functions
225.Fn getpwent ,
226.Fn getpwnam ,
227and
228.Fn getpwuid ,
229leave their results in an internal static object and return
230a pointer to that object.
231Subsequent calls to
232the same function
233will modify the same object.
234.Pp
235The functions
236.Fn getpwent ,
237.Fn endpwent ,
238.Fn setpassent ,
239and
240.Fn setpwent
241are fairly useless in a networked environment and should be
242avoided, if possible.