Response code "482" / XPATH
Russ Allbery
rra at stanford.edu
Tue Dec 3 20:27:41 UTC 2002
bill davidsen <davidsen at tmr.com> writes:
> Russ Allbery <rra at stanford.edu> wrote:
> | 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.
Yes, but usually that's for readers. I was referring to the innd AUTHINFO
support, which ignores usernames, only cares about passwords, has no
module support, and only checks against passwords in incoming.conf.
--
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
More information about the inn-workers
mailing list