Message 121092 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	eric.araujo, jelie, pitrou, r.david.murray
Date	2010-11-12.23:44:24
SpamBayes Score	3.0696418e-05
Marked as misclassified	No
Message-id	<1289605456.3525.3.camel@localhost.localdomain>
In-reply-to	<1289604872.15.0.357130822508.issue10284@psf.upfronthosting.co.za>

Content
Hello Julien, > That's one of the reasons why AUTHINFO SASL is better than AUTHINFO > USER. It also allows whitespaces (a few news servers do not parse > well whitespaces in user names or passwords after AUTHINFO USER/PASS > -- imagine " test" with a leading space). Solved with SASL. If you want to contribute SASL auth for NNTP, it might make sense to have a dedicated module to provide SASL mechanisms (and then let imaplib reuse that module). Of course, not all mechanisms need to be provided at the start. (FWIW, I had written a patch providing generic SASL support for Twisted years ago: http://twistedmatrix.com/trac/ticket/2015 )

Hello Julien,

> That's one of the reasons why AUTHINFO SASL is better than AUTHINFO
> USER.  It also allows whitespaces (a few news servers do not parse
> well whitespaces in user names or passwords after AUTHINFO USER/PASS
> -- imagine " test" with a leading space).  Solved with SASL.

If you want to contribute SASL auth for NNTP, it might make sense to
have a dedicated module to provide SASL mechanisms (and then let imaplib
reuse that module). Of course, not all mechanisms need to be provided at
the start.

(FWIW, I had written a patch providing generic SASL support for Twisted
years ago: http://twistedmatrix.com/trac/ticket/2015 )

History
Date	User	Action	Args
2010-11-12 23:44:25	pitrou	set	recipients: + pitrou, eric.araujo, r.david.murray, jelie
2010-11-12 23:44:24	pitrou	link	issue10284 messages
2010-11-12 23:44:24	pitrou	create