Message 216690 - 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	ctheune
Recipients	amaury.forgeotdarc, ctheune, guettli, pconnell, r.david.murray
Date	2014-04-17.14:31:55
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1397745115.3.0.650120393767.issue12489@psf.upfronthosting.co.za>
In-reply-to

Content
So, in addition to "+/" and "-_" there are quite a few base64 variants. Worst thing: there are the two ambigious variants "-_" and "_-", even though "_-" supposedly is "non-standard" for its use. See http://en.wikipedia.org/wiki/Base64 The shortest fix I can see would be to not use binascii directly from the email module but go through the base64 module (as pointed out by the blogpost) and call the urlsafe version. That should catch both cases. Preparing a patch right now.

So, in addition to "+/" and "-_" there are quite a few base64 variants. Worst thing: there are the two ambigious variants "-_" and "_-", even though "_-" supposedly is "non-standard" for its use.

See http://en.wikipedia.org/wiki/Base64

The shortest fix I can see would be to not use binascii directly from the email module but go through the base64 module (as pointed out by the blogpost) and call the urlsafe version. That should catch both cases.

Preparing a patch right now.

History
Date	User	Action	Args
2014-04-17 14:31:55	ctheune	set	recipients: + ctheune, guettli, amaury.forgeotdarc, r.david.murray, pconnell
2014-04-17 14:31:55	ctheune	set	messageid: <1397745115.3.0.650120393767.issue12489@psf.upfronthosting.co.za>
2014-04-17 14:31:55	ctheune	link	issue12489 messages
2014-04-17 14:31:55	ctheune	create