icon Top 9 categories map      RocketAware > man pages >

rexecd(8)

Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.


The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Home

Search all pages


Subjects

By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Math
Integer, Floating point, Matrix, Statistics, Boolean, ...

Processing
Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Communications
Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

    

RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD Others



REXECD(8)               OpenBSD System Manager's Manual              REXECD(8)

NAME
     rexecd - remote execution server



SYNOPSIS
     rexecd

DESCRIPTION
     Rexecd is the server for the rexec(3) routine.  The server provides re-
     mote execution facilities with authentication based on user names and
     passwords.

     Rexecd listens for service requests at the port indicated in the ``exec''
     service specification; see services(5).  When a service request is re-
     ceived the following protocol is initiated:

     1.   The server reads characters from the socket up to a NUL (`\0') byte.
          The resultant string is interpreted as an ASCII number, base 10.

     2.   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 stderr. A
          second connection is then created to the specified port on the
          client's machine.

     3.   A NUL terminated user name of at most 16 characters is retrieved on
          the initial socket.

     4.   A NUL terminated, unencrypted password of at most 16 characters is
          retrieved on the initial socket.

     5.   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.

     6.   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 mes-
          sage returned.

     7.   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 rexecd.

DIAGNOSTICS
     Except for the last one listed below, all diagnostic messages are re-
     turned 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 pri-
     or to the command execution).

     username too long
             The name is longer than 16 characters.

     password too long
             The password is longer than 16 characters.

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

     Login incorrect.
             No password file entry for the user name existed or the wrong

             password was supplied.

     No remote directory.
             The chdir command to the home directory failed.

     Try again.
             A fork by the server failed.

     <shellname>: ...
             The user's login shell could not be started.  This message is re-
             turned on the connection associated with the stderr, and is not
             preceded by a flag byte.

SEE ALSO
     rexec(3)

BUGS
     Do not enable rexecd.

HISTORY
     The rexecd command appeared in 4.2BSD.

4.2 Berkeley Distribution       March 16, 1991                               2

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.



(Corrections, notes, and links courtesy of RocketAware.com)


[Detailed Topics]
FreeBSD Sources for rexecd(8)
OpenBSD sources for rexecd(8)


[Overview Topics]

Up to: Remote Process Creation and Control - Methods of starting and controlling processes remotely. (telnet, login, rexec, et al.)


RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD Others






Rapid-Links: Search | About | Comments | Submit Path: RocketAware > man pages > rexecd.8/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments