Message 150496 - 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	r.david.murray
Recipients	docs@python, etukia, r.david.murray
Date	2012-01-03.03:18:01
SpamBayes Score	0.009205721
Marked as misclassified	No
Message-id	<1325560682.04.0.164895039767.issue13700@psf.upfronthosting.co.za>
In-reply-to

Content
Bytes definitely. We hashed that out a while ago. My point is that CRAM_MD5 login calls authenticate, and its authenticator returns a string, just like your example does. So it ought to be going through the same code path. I haven't followed the logic in detail, though, so there must be some difference...I'm pretty sure the MD5 login has a test now (but not 100% sure...)

Bytes definitely.  We hashed that out a while ago.

My point is that CRAM_MD5 login calls authenticate, and its authenticator returns a string, just like your example does.  So it ought to be going through the same code path.  I haven't followed the logic in detail, though, so there must be some difference...I'm pretty sure the MD5 login has a test now (but not 100% sure...)

History
Date	User	Action	Args
2012-01-03 03:18:02	r.david.murray	set	recipients: + r.david.murray, docs@python, etukia
2012-01-03 03:18:02	r.david.murray	set	messageid: <1325560682.04.0.164895039767.issue13700@psf.upfronthosting.co.za>
2012-01-03 03:18:01	r.david.murray	link	issue13700 messages
2012-01-03 03:18:01	r.david.murray	create