BSD 4_3_Net_2 release

[unix-history] / usr / src / libexec / rexecd / rexecd.8

diff --git a/usr/src/libexec/rexecd/rexecd.8 b/usr/src/libexec/rexecd/rexecd.8
index bf5055f..8aee1d9 100644 (file)
--- a/usr/src/libexec/rexecd/rexecd.8
+++ b/usr/src/libexec/rexecd/rexecd.8
@@ -1,134 +1,148 @@
-.\" Copyright (c) 1983 The Regents of the University of California.
+.\" Copyright (c) 1983, 1991 The Regents of the University of California.

 .\" All rights reserved.
 .\"
 .\" All rights reserved.
 .\"

-.\" Redistribution and use in source and binary forms are permitted provided
-.\" that: (1) source distributions retain this entire copyright notice and
-.\" comment, and (2) distributions including binaries display the following
-.\" acknowledgement:  ``This product includes software developed by the
-.\" University of California, Berkeley and its contributors'' in the
-.\" documentation or other materials provided with the distribution and in
-.\" all advertising materials mentioning features or use of this software.
-.\" 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 ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
-.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 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.

 .\"
 .\"

-.\"    @(#)rexecd.8    6.4 (Berkeley) 6/24/90
+.\" 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
+.\" SUCH DAMAGE.

 .\"
 .\"

-.TH REXECD 8 "June 24, 1990"
-.UC 5
-.SH NAME
-rexecd \- remote execution server
-.SH SYNOPSIS
-.B rexecd
-.SH DESCRIPTION
-.I Rexecd
+.\"     @(#)rexecd.8   6.5 (Berkeley) 3/16/91
+.\"
+.Dd March 16, 1991
+.Dt REXECD 8
+.Os BSD 4.2
+.Sh NAME
+.Nm rexecd
+.Nd remote execution server
+.Sh SYNOPSIS
+.Nm rexecd
+.Sh DESCRIPTION
+.Nm Rexecd

 is the server for the 
 is the server for the 

-.IR rexec (3)
+.Xr rexec 3

 routine.  The server provides remote execution facilities
 with authentication based on user names and
 passwords.
 routine.  The server provides remote execution facilities
 with authentication based on user names and
 passwords.

-.PP
-.I Rexecd
+.Pp
+.Nm Rexecd

 listens for service requests at the port indicated in
 the ``exec'' service specification; see
 listens for service requests at the port indicated in
 the ``exec'' service specification; see

-.IR services (5).
+.Xr services 5 .

 When a service request is received the following protocol
 is initiated:
 When a service request is received the following protocol
 is initiated:

-.IP 1)
+.Bl -enum
+.It

 The server reads characters from the socket up
 The server reads characters from the socket up

-to a null (`\e0') byte.  The resultant string is
-interpreted as an ASCII number, base 10.
-.IP 2)
+to a NUL
+.Pq Ql \e0
+byte.  The resultant string is
+interpreted as an
+.Tn ASCII
+number, base 10.
+.It 

 If the number received in step 1 is non-zero,
 it is interpreted as the port number of a secondary
 stream to be used for the 
 If the number received in step 1 is non-zero,
 it is interpreted as the port number of a secondary
 stream to be used for the 

-.BR stderr .
+.Em stderr .

 A second connection is then created to the specified
 port on the client's machine.
 A second connection is then created to the specified
 port on the client's machine.

-.IP 3)
-A null terminated user name of at most 16 characters
+.It
+A NUL terminated user name of at most 16 characters

 is retrieved on the initial socket.
 is retrieved on the initial socket.

-.IP 4)
-A null terminated, unencrypted password of at most
+.It
+A NUL terminated, unencrypted password of at most

 16 characters is retrieved on the initial socket.  
 16 characters is retrieved on the initial socket.  

-.IP 5)
-A null terminated command to be passed to a
+.It
+A NUL terminated command to be passed to a

 shell is retrieved on the initial socket.  The length of
 the command is limited by the upper bound on the size of
 the system's argument list.  
 shell is retrieved on the initial socket.  The length of
 the command is limited by the upper bound on the size of
 the system's argument list.  

-.IP 6)
-.I Rexecd
+.It
+.Nm Rexecd

 then validates the user as is done at login time
 and, if the authentication was successful, changes
 to the user's home directory, and establishes the user
 and group protections of the user.
 If any of these steps fail the connection is
 aborted with a diagnostic message returned.
 then validates the user as is done at login time
 and, if the authentication was successful, changes
 to the user's home directory, and establishes the user
 and group protections of the user.
 If any of these steps fail the connection is
 aborted with a diagnostic message returned.

-.IP 7)
-A null byte is returned on the initial socket
+.It
+A NUL byte is returned on the initial socket

 and the command line is passed to the normal login
 shell of the user.  The
 shell inherits the network connections established
 by
 and the command line is passed to the normal login
 shell of the user.  The
 shell inherits the network connections established
 by

-.IR rexecd .
-.SH DIAGNOSTICS
+.Nm rexecd .
+.El
+.Sh DIAGNOSTICS

 Except for the last one listed below,
 all diagnostic messages are returned on the initial socket,
 after which any network connections are closed.
 An error is indicated by a leading byte with a value of
 1 (0 is returned in step 7 above upon successful completion
 of all the steps prior to the command execution).
 Except for the last one listed below,
 all diagnostic messages are returned on the initial socket,
 after which any network connections are closed.
 An error is indicated by a leading byte with a value of
 1 (0 is returned in step 7 above upon successful completion
 of all the steps prior to the command execution).

-.PP
-.B ``username too long''
-.br
+.Pp
+.Bl -tag -width Ds
+.It Sy username too long

 The name is
 longer than 16 characters.
 The name is
 longer than 16 characters.

-.PP
-.B ``password too long''
-.br
+.It Sy password too long

 The password is longer than 16 characters.
 The password is longer than 16 characters.

-.PP
-.B ``command too long ''
-.br
+.It Sy command too long

 The command line passed exceeds the size of the argument
 list (as configured into the system).
 The command line passed exceeds the size of the argument
 list (as configured into the system).

-.PP
-.B ``Login incorrect.''
-.br
+.It Sy Login incorrect.

 No password file entry for the user name existed.
 No password file entry for the user name existed.

-.PP
-.B ``Password incorrect.''
-.br
+.It Sy Password incorrect.

 The wrong was password supplied.
 The wrong was password supplied.

-.PP
-.B ``No remote directory.''
-.br
+.It Sy \&No remote directory.

 The 
 The 

-.I chdir
+.Xr chdir

 command to the home directory failed.
 command to the home directory failed.

-.PP
-.B ``Try again.''
-.br
+.It Sy Try again.

 A
 A

-.I fork
+.Xr fork

 by the server failed.
 by the server failed.

-.PP
-.B ``<shellname>: ...''
-.br
+.It Sy <shellname>: ...

 The user's login shell could not be started.
 This message is returned
 on the connection associated with the
 The user's login shell could not be started.
 This message is returned
 on the connection associated with the

-.BR stderr ,
+.Em stderr ,

 and is not preceded by a flag byte.
 and is not preceded by a flag byte.

-.SH SEE ALSO
-rexec(3)
-.SH BUGS
+.El
+.Sh SEE ALSO
+.Xr rexec 3
+.Sh BUGS

 Indicating ``Login incorrect'' as opposed to ``Password incorrect''
 is a security breach which allows people to probe a system for users
 with null passwords.
 Indicating ``Login incorrect'' as opposed to ``Password incorrect''
 is a security breach which allows people to probe a system for users
 with null passwords.

-.PP
+.Pp

 A facility to allow all data and password exchanges to be encrypted should be
 present.
 A facility to allow all data and password exchanges to be encrypted should be
 present.

+.Sh HISTORY
+The
+.Nm
+command appeared in
+.Bx 4.2 .