From owner-freebsd-stable Wed Jun 16 11:19:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.aepnet.com (ns1.aepnet.com [208.129.247.1]) by hub.freebsd.org (Postfix) with ESMTP id 9959814DE8; Wed, 16 Jun 1999 11:19:25 -0700 (PDT) (envelope-from chris@ns1.aepnet.com) Received: from localhost (chris@localhost) by ns1.aepnet.com (8.8.7/8.8.7) with ESMTP id LAA26966; Wed, 16 Jun 1999 11:11:59 -0700 Date: Wed, 16 Jun 1999 11:11:59 -0700 (MST) From: chris To: Dag-Erling Smorgrav Cc: kip@lyris.com, "David O'Brien" , Holtor , freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD's FTP Daemon In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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