RFC 912 UNKNOWN TCP · AUTHENTICATION · NETWORKING

Authentication service

A proposed TCP service that identifies the owner of a connection on the server system.

On rfc-editor.org ↗
PUBLISHED
September 1984
AUTHORS
M. St. Johns
STREAM
Legacy
OBSOLETED BY
RFC 931 — Authentication server
SERVER TCP PORT
113
QUERY CONTENTS
Local and foreign TCP ports
RESPONSE TYPES
USERID or ERROR
DOI
10.17487/RFC0912

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                       Mike StJohns
Request for Comments: 912                                           TPSC
                                                          September 1984

                         Authentication Service


STATUS OF THIS MEMO

   This RFC suggests a proposed protocol for the ARPA-Internet
   community, and  requests discussion and suggestions for improvements.
   Distribution of this memo is unlimited.

INTRODUCTION

   The Authentication Server provides a means to determine the identity
   of a user of a particular TCP connection.  Given a TCP port number
   pair, it returns a character string which identifies the owner of
   that connection on the server's system.  Suggested uses include
   automatic identification and verification of a user during an FTP
   session, additional verification of a TAC dial up user, and access
   verification for a generalized network file server.

OVERVIEW

   This is a connection based application on TCP.  A server listens for
   TCP connections on TCP port 113 (decimal).  Once a connection is
   established, the server reads one line of data which specifies the
   connection of interest.  If it exists, the system dependent user
   identifier of the connection of interest is sent out the connection.
   The service closes the connection after sending the user identifier.

RESTRICTIONS

   Queries are permitted only for fully specified connections.  The
   local/foreign host pair used to fully specify the connection are
   taken from the query connection.  This means a user on Host A may
   only query the server on Host B about connections between A and B.

QUERY/RESPONSE FORMAT

   The server accepts simple text query requests of the form

      <local-port>, <foreign-port>

   where <local-port>, is the TCP port (decimal) on the target (server)
   system, and <foreign-port> is the TCP port (decimal) on the source
   (user) system.

      For example:

Authentication Service


         23, 6191

   The response is of the form

      <local-port>, <foreign-port> : <response-type> : <additional-info>

   where <local-port>, <foreign-port> are the same pair as the query,
   <response-type> is a keyword identifying the type of response, and
   <additional info> is context dependent.

      For example:

         23, 6191 : USERID : StJohns

RESPONSE TYPES

   A response can be one of two types:

   USERID

      In this case, <additional-info> is the printable representation of
      the user identifier of the owner of the connection.  The format of
      the returned user identifier is completely system dependent.

   ERROR

      For some reason the owner of the TCP port could not be determined,
      <additional-info> tells why.  The following are suggested values
      of <additional-info> and their meanings.

         INVALID PORT

            Either the local or foreign port was improperly specified.

         NO USER

            The connection specified by the port pair is not currently
            in use.

         UNKNOWN ERROR

            Can't determine connection owner; reason unknown.
            Other values may be specified as necessary.

Authentication Service


CAVEATS

   Unfortunately, the trustworthiness of the various host systems that
   might implement an authentication server will vary quite a bit.  It
   is up to the various applications that will use the server to
   determine the amount of trust they will place in the returned
   information.  It may be appropriate in some cases restrict the use of
   the server to within a locally controlled subnet.

APPLICATIONS

   1) Automatic user authentication for FTP.

   2) Verification for privileged network operations.  For example,
   having the server start or stop special purpose servers.

DISCLAIMER

   I designed this protocol to allow me to eliminate the bother of
   having to identify myself before continuing an FTP session.

   Since I started work on it, other applications appeared.  I have
   tried to consider all of our applications while still making this as
   general as possible.

ISO Plain Language

On this page
PROBLEMApplications needed a way to ask a host which user owned a specified TCP connection on that host.
MECHANISMThe proposed server listens on TCP port 113, receives a pair of port numbers, and returns a system-dependent user identifier or an error.
HISTORICAL CONTEXTRFC 912 is an informational proposal and was obsoleted by RFC 931.

§1Purpose and Connection Rules

The Authentication Server is intended to identify the owner of a particular TCP connection on the server's system. Suggested uses include identifying a user during FTP and checking a user for network file-server access.

The service listens on TCP port 113. Queries are allowed only for fully specified connections: a user on Host A can ask Host B about connections between A and B, using the query connection to supply the host pair.

A client asks the server who owns one of its TCP connections. The query can cover a connection between the client host and the server host.

§2Queries and Responses

The client sends one text line containing the local and foreign TCP ports, separated by a comma. The local port is on the target server system; the foreign port is on the source user system. For example, the RFC shows 23, 6191.

The server responds with the same port pair, a response type, and additional information. USERID returns a printable identifier whose format is system-dependent. ERROR can include INVALID PORT, NO USER, or UNKNOWN ERROR. The server closes the connection after responding.

Send the two port numbers in a text line. The server returns a user identifier or an error explaining why it could not determine one.

§3Trust in the Response

The RFC warns that authentication servers may differ in trustworthiness. Applications must decide how much trust to place in the returned information. It says that, in some cases, use may appropriately be restricted to a locally controlled subnet.

The memo lists automatic user authentication for FTP and verification for privileged network operations as possible applications. It does not itself make the returned identity trustworthy.

A returned name is only as reliable as the server that supplies it. Applications must decide whether to trust that server before using the answer.