Your message dated Mon, 25 Jun 2012 02:24:09 +0200
with message-id <[email protected]>
and subject line Re: Bug#652642: tin tries AUTHINFO USER before AUTHINFO GENERIC
has caused the Debian Bug report #652642,
regarding tin tries AUTHINFO USER before AUTHINFO GENERIC
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
652642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652642
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tin
Version: 1:1.9.6~20100522-1

My news server does not implement CAPABILITIES.  This results in tin
trying to authenticate.  (This is of course a bug in itself.)

When it tries to do this authentication, it prompts the user for a
username and password and then uses AUTHINFO USER.  However, I have
NNTPAUTH set and my server uses AUTHINFO GENERIC.  So tin should, if
it wants to authenticate, do AUTHINFO GENERIC.

This seems to be a regression of #85274.

I will return to lenny's tin for now, but I'm happy to try versions
from sid or experimental provided they build on squeeze.

Thanks,
Ian.

-- 
Ian Jackson                  personal email: <[email protected]>
These opinions are my own.        http://www.chiark.greenend.org.uk/~ijackson/
PGP2 key 1024R/0x23f5addb,     fingerprint 5906F687 BD03ACAD 0D8E602E FCF37657



--- End Message ---
--- Begin Message ---
On Dec 19, Urs Janßen <[email protected]> wrote:

> AUTHINFO GENERIC was removed from tin (starting with 1.9.5) as it's
> deprecated by RFC 4643.
Since AUTHINFO GENERIC is not supported anymore I am closing this bug.

-- 
ciao,
Marco

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to