Date: Wed, 16 Jun 1999 11:11:59 -0700 (MST) From: chris <chris@ns1.aepnet.com> To: Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: kip@lyris.com, "David O'Brien" <obrien@FreeBSD.ORG>, Holtor <holtor@yahoo.com>, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD's FTP Daemon Message-ID: <Pine.LNX.4.04.9906161105460.25009-100000@ns1.aepnet.com> In-Reply-To: <xzpd7ywego6.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 Jun 1999, Dag-Erling Smorgrav wrote:
> kip@lyris.com writes:
> > Based on the documentation what leads you to believe that the author of
> > NcFTP does not understand RFC 931? Were you just being inflammatory?
>
> RFC931? What does that have to do with anything?
>
hehe, that's a good question:
0931 Authentication server. M. St. Johns. Jan-01-1985. (Format:
TXT=8982 bytes) (Obsoletes RFC0912) (Status: UNKNOWN)
>
> As for the man page, read it yourself and make up your own mind. If
> the author had read RFC959, he wouldn't have to invent his own
> vocabulary as he went along.
>
0959 File Transfer Protocol. J. Postel, J.K. Reynolds. Oct-01-1985.
(Format: TXT=151249 bytes) (Obsoletes RFC0765) (Updated by RFC2228)
(Status: STANDARD)
>
> DES
> --
> Dag-Erling Smorgrav - des@flood.ping.uio.no
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
it is rather a trip to read though:
Network Working Group Mike StJohns
Request for Comments: 931 TPSC
Supersedes: RFC 912 January 1985
Authentication Server
STATUS OF THIS MEMO
This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.
This is the second draft of this proposal (superseding RFC 912) and
incorporates a more formal description of the syntax for the request
and response dialog, as well as a change to specify the type of user
identification returned. Distribution of this memo is unlimited.
INTRODUCTION
The Authentication Server Protocol 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.
...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.04.9906161105460.25009-100000>