Xref: utzoo comp.protocols.tcp-ip:7012 comp.sources.wanted:7262
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!rutgers!njin!princeton!phoenix!bernsten
From: bernsten@phoenix.Princeton.EDU (Dan Bernstein)
Newsgroups: comp.protocols.tcp-ip,comp.sources.wanted
Subject: BSD UNIX authd
Message-ID: <8145@phoenix.Princeton.EDU>
Date: 4 May 89 21:44:56 GMT
Reply-To: bernsten@phoenix.Princeton.EDU (Dan Bernstein)
Followup-To: comp.protocols.tcp-ip
Distribution: usa
Organization: Hmph.
Lines: 19

Does anyone have a working BSD 4.2 or 4.3 authentication daemon?
As per RFC 931, the daemon should accept connections to port 113
(directly or through inetd), read a line of two numbers as in

  6191,23

and output a line like one of

  6191,23:USERID:UNIX:shmoe
  6191,23:ERROR:NO-USER

where ``shmoe'' is the owner (on the client machine) of the connection
between port 6191 on the server and port 23 on the client. (Notes: (1)
The example in the RFC has the client requesting ``23,6191'', which seems
a bit weird. (2) Whitespace can be put anywhere. (3) All of \,: must be
backslash-escaped within the userid. (4) The RFC doesn't specify very
well what a ``line'' is but CR LF is probably safe.)

---Dan Bernstein, bernsten@phoenix.princeton.edu