xref: /dragonfly/lib/libc/sys/getlogin.2 (revision 6e285212)
1.\" Copyright (c) 1989, 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.\"	@(#)getlogin.2	8.1 (Berkeley) 6/9/93
33.\" $FreeBSD: src/lib/libc/sys/getlogin.2,v 1.14.2.6 2001/12/14 18:34:00 ru Exp $
34.\" $DragonFly: src/lib/libc/sys/getlogin.2,v 1.2 2003/06/17 04:26:47 dillon Exp $
35.\"
36.Dd June 9, 1993
37.Dt GETLOGIN 2
38.Os
39.Sh NAME
40.Nm getlogin ,
41.Nm getlogin_r ,
42.Nm setlogin
43.Nd get/set login name
44.Sh LIBRARY
45.Lb libc
46.Sh SYNOPSIS
47.In unistd.h
48.Ft char *
49.Fn getlogin void
50.In sys/param.h
51.Ft int
52.Fn getlogin_r "char *name" "int len"
53.Ft int
54.Fn setlogin "const char *name"
55.Sh DESCRIPTION
56The
57.Fn getlogin
58routine
59returns the login name of the user associated with the current session,
60as previously set by
61.Fn setlogin .
62The name is normally associated with a login shell
63at the time a session is created,
64and is inherited by all processes descended from the login shell.
65(This is true even if some of those processes assume another user ID,
66for example when
67.Xr su 1
68is used).
69.Pp
70.Fn getlogin_r
71provides the same service as
72.Fn getlogin
73except the caller must provide the buffer
74.Fa name
75with length
76.Fa len
77bytes
78to hold the result.  The buffer should be at least
79.Dv MAXLOGNAME
80bytes in length.
81.Pp
82.Fn Setlogin
83sets the login name of the user associated with the current session to
84.Fa name .
85This call is restricted to the super-user, and
86is normally used only when a new session is being created on behalf
87of the named user
88(for example, at login time, or when a remote shell is invoked).
89.Pp
90.Em NOTE :
91There is only one login name per session.
92.Pp
93It is
94.Em CRITICALLY
95important to ensure that
96.Fn setlogin
97is only ever called after the process has taken adequate steps to ensure
98that it is detached from its parent's session.
99Making a
100.Fn setsid
101system call is the
102.Em ONLY
103way to do this.  The
104.Fn daemon
105library call calls
106.Fn setsid
107which is an ideal way of detaching from a controlling terminal and
108forking into the background.
109.Pp
110In particular, doing a
111.Fn ioctl ttyfd TIOCNOTTY ...\&
112or
113.Fn setpgrp ...\&
114is
115.Em NOT
116sufficient.
117.Pp
118Once a parent process does a
119.Fn setsid
120call, it is acceptable for some child of that process to then do a
121.Fn setlogin
122even though it is not the session leader, but beware that ALL processes
123in the session will change their login name at the same time, even the
124parent.
125.Pp
126This is not the same as the traditional UNIX behavior of inheriting privilege.
127.Pp
128Since the
129.Fn setlogin
130system call is restricted to the super-user, it is assumed that (like
131all other privileged programs) the programmer has taken adequate
132precautions to prevent security violations.
133.Sh RETURN VALUES
134If a call to
135.Fn getlogin
136succeeds, it returns a pointer to a null-terminated string in a static buffer,
137or
138.Dv NULL
139if the name has not been set.
140.Fn getlogin_r
141returns zero if successful, or the error number upon failure.
142.Pp
143.Rv -std setlogin
144.Sh ERRORS
145The following errors may be returned by these calls:
146.Bl -tag -width Er
147.It Bq Er EFAULT
148The
149.Fa name
150parameter gave an
151invalid address.
152.It Bq Er EINVAL
153The
154.Fa name
155parameter
156pointed to a string that was too long.
157Login names are limited to
158.Dv MAXLOGNAME
159(from
160.Ao Pa sys/param.h Ac )
161characters, currently 17 including null.
162.It Bq Er EPERM
163The caller tried to set the login name and was not the super-user.
164.It Bq Er ERANGE
165The size of the buffer is smaller than the result to be returned.
166.El
167.Sh SEE ALSO
168.Xr setsid 2 ,
169.Xr daemon 3
170.Sh BUGS
171In earlier versions of the system,
172.Fn getlogin
173failed unless the process was associated with a login terminal.
174The current implementation (using
175.Fn setlogin )
176allows getlogin to succeed even when the process has no controlling terminal.
177In earlier versions of the system, the value returned by
178.Fn getlogin
179could not be trusted without checking the user ID.
180Portable programs should probably still make this check.
181.Sh HISTORY
182The
183.Fn getlogin
184function first appeared in
185.Bx 4.4 .
186The return value of
187.Fn getlogin_r
188was changed from earlier versions of
189.Fx
190to be conformant with
191.St -p1003.1-96 .
192.Sh STANDARDS
193.Fn getlogin
194and
195.Fn getlogin_r
196conform to
197.St -p1003.1-96 .
198