IETF Logo Mail Archive

Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF

Brian Hernacki <bhern@netscape.com> Thu, 19 December 1996 17:33 UTC

Received: from cnri by ietf.org id aa09069; 19 Dec 96 12:33 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa14924; 19 Dec 96 12:33 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id LAA15840 for ietf-nntp-outgoing; Thu, 19 Dec 1996 11:28:36 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.3/8.7.3) with ESMTP id LAA15835 for <ietf-nntp@ACADEM2.ACADEM.COM>; Thu, 19 Dec 1996 11:28:34 -0600 (CST)
Received: from c3po.mcom.com (h-205-217-237-46.netscape.com [205.217.237.46]) by academ.com (8.8.3/8.7.1) with ESMTP id LAA14984 for <ietf-nntp@academ.com>; Thu, 19 Dec 1996 11:28:33 -0600 (CST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by c3po.mcom.com (8.7.5/8.7.3) with ESMTP id JAA03582 for <ietf-nntp@academ.com>; Thu, 19 Dec 1996 09:28:01 -0800 (PST)
Received: from ventnor.mcom.com ([207.1.137.53]) by dredd.mcom.com (Netscape Mail Server v2.02) with SMTP id AAA12016; Thu, 19 Dec 1996 09:28:01 -0800
Message-ID: <32B97B56.CA2@netscape.com>
Date: Thu, 19 Dec 1996 09:28:54 -0800
From: Brian Hernacki <bhern@netscape.com>
Organization: Netscape, Floating Point Division
X-Mailer: Mozilla 3.0GoldC (X11; U; SunOS 5.5 sun4u)
MIME-Version: 1.0
To: Nat Ballou <NatBa@microsoft.com>
CC: Brian Kantor <brian@nothing.ucsd.edu>, Chris.Newman@innosoft.com, moore@cs.utk.edu, ietf-nntp@academ.com
Subject: Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF
References: <038c034311613c6IMSMAIL@ims.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Nat Ballou wrote:
> 
> > From: Brian Kantor <brian@nothing.ucsd.edu>
> > To: Chris.Newman@INNOSOFT.COM; moore@cs.utk.edu
> > Cc: ietf-nntp@academ.com
> > Subject: Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF
> > Date: Thursday, December 19, 1996 7:07 AM
> >
> > Gentlemen,
> >
> > Please do not forget that AUTHINFO USER does NOT REQUIRE A PASSWORD.
> >
> > I originally added it to facilitate gathering of readership statistics,
> > and in that application, it needed only supply the username.
> >
> > While AUTHINFO may be used to control access, that is not its only use.
> 
> While that might have been the intent, I believe every implementation
> requires an AUTHINFO PASS after an AUTHINFO USER.  I may be wrong here
> - but if I'm right, I'd rather RFC977 driven by current practices rather
> than intentions.
> 
> So - are there any implementations that accept AUTHINFO USER without an
> AUTHINFO PASS?

As far as protocol goes, Netscape News Server will accept an AUTHINFO
USER, return a "381 PASS required", but still allow you to enter other
commands without having entered AUTHINFO PASS. It does not however, use
the USER information (even for readership stats) unless a password has
been provided to prove identity.

--brian

v2.8.7 | Report a Bug | By Email