Response code "482" / XPATH

bill davidsen davidsen at tmr.com
Tue Dec 3 19:30:18 UTC 2002


In article <ylel8zvjku.fsf at windlord.stanford.edu>,
Russ Allbery  <rra at stanford.edu> wrote:
| 
| Bettina Fink <laura at hydrophil.de> writes:

| > b). Response code "482"
| 
| > | 3.1.1 Original AUTHINFO
| > | [...]
| > | The 482 code will also be returned when the AUTHINFO commands are not
| > | entered in the correct sequence (like two AUTHINFO USERs in a row, or
| > | AUTHINFO PASS preceding AUTHINFO USER).
| 
| > 200 [server] InterNetNews NNRP server INN 2.3.2 (20010320 prerelease) ready (posting ok).
| > authinfo user blah
| > 381 PASS required
| > authinfo user blah
| > 381 PASS required
| 
| I've added this to doc/compliance-nntp.  It's a fairly low-priority
| problem, since the reason why innd behaves this way is because it doesn't
| care about the username at all.  innd AUTHINFO support is a *very*
| simplified affair, and I'm not sure how widely it's used.

  More rather than less, I think. With the advent of DHCP it has become
harder to tell a legitimate user by IP, and thus more use of AUTHINFO is
likely. Haven't looked at how well the Radius and LDAP auth work below
it, I centainly was satisfied using my own auth module and method.


-- 
bill davidsen <davidsen at tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


More information about the inn-workers mailing list