]> git.saurik.com Git - apple/network_cmds.git/blame - rexecd.tproj/rexecd.8
network_cmds-176.tar.gz
[apple/network_cmds.git] / rexecd.tproj / rexecd.8
CommitLineData
b7080c8e
A
1.\" Copyright (c) 1983, 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.\" @(#)rexecd.8 8.3 (Berkeley) 6/1/94
33.\"
34.Dd June 1, 1994
35.Dt REXECD 8
36.Os BSD 4.2
37.Sh NAME
38.Nm rexecd
39.Nd remote execution server
40.Sh SYNOPSIS
41.Nm rexecd
42.Sh DESCRIPTION
43.Nm Rexecd
44is the server for the
45.Xr rexec 3
46routine. The server provides remote execution facilities
47with authentication based on user names and
48passwords.
49.Pp
50.Nm Rexecd
51listens for service requests at the port indicated in
52the ``exec'' service specification; see
53.Xr services 5 .
54When a service request is received the following protocol
55is initiated:
56.Bl -enum
57.It
58The server reads characters from the socket up
59to a NUL
60.Pq Ql \e0
61byte. The resultant string is
62interpreted as an
63.Tn ASCII
64number, base 10.
65.It
66If the number received in step 1 is non-zero,
67it is interpreted as the port number of a secondary
68stream to be used for the
69.Em stderr .
70A second connection is then created to the specified
71port on the client's machine.
72.It
73A NUL terminated user name of at most 16 characters
74is retrieved on the initial socket.
75.It
76A NUL terminated, unencrypted password of at most
7716 characters is retrieved on the initial socket.
78.It
79A NUL terminated command to be passed to a
80shell is retrieved on the initial socket. The length of
81the command is limited by the upper bound on the size of
82the system's argument list.
83.It
84.Nm Rexecd
85then validates the user as is done at login time
86and, if the authentication was successful, changes
87to the user's home directory, and establishes the user
88and group protections of the user.
89If any of these steps fail the connection is
90aborted with a diagnostic message returned.
91.It
92A NUL byte is returned on the initial socket
93and the command line is passed to the normal login
94shell of the user. The
95shell inherits the network connections established
96by
97.Nm rexecd .
98.El
99.Sh DIAGNOSTICS
100Except for the last one listed below,
101all diagnostic messages are returned on the initial socket,
102after which any network connections are closed.
103An error is indicated by a leading byte with a value of
1041 (0 is returned in step 7 above upon successful completion
105of all the steps prior to the command execution).
106.Pp
107.Bl -tag -width Ds
108.It Sy username too long
109The name is
110longer than 16 characters.
111.It Sy password too long
112The password is longer than 16 characters.
113.It Sy command too long
114The command line passed exceeds the size of the argument
115list (as configured into the system).
116.It Sy Login incorrect.
117No password file entry for the user name existed.
118.It Sy Password incorrect.
119The wrong password was supplied.
120.ne 1i
121.It Sy \&No remote directory.
122The
123.Xr chdir
124command to the home directory failed.
125.It Sy Try again.
126A
127.Xr fork
128by the server failed.
129.It Sy <shellname>: ...
130The user's login shell could not be started.
131This message is returned
132on the connection associated with the
133.Em stderr ,
134and is not preceded by a flag byte.
135.El
136.Sh SEE ALSO
137.Xr rexec 3
138.Sh BUGS
139Indicating ``Login incorrect'' as opposed to ``Password incorrect''
140is a security breach which allows people to probe a system for users
141with null passwords.
142.Pp
143A facility to allow all data and password exchanges to be encrypted should be
144present.
145.Sh HISTORY
146The
147.Nm
148command appeared in
149.Bx 4.2 .