➜

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 serhiy.storchaka
Recipients docs@python, paulehoffman, serhiy.storchaka
Date 2019-04-23.18:25:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1556043922.99.0.58094619179.issue36700@roundup.psfhosted.org>
In-reply-to
Content 
base64 supports RFC 3548, but not RFC 4648.

=====================================================================
13.  Changes Since RFC 3548

   Added the "base32 extended hex alphabet", needed to preserve sort
   order of encoded data.

   Referenced IMAP for the special Base64 encoding used there.

   Fixed the example copied from RFC 2440.

   Added security consideration about providing a signature for
   cryptoanalysis.

   Added test vectors.

   Fixed typos.
=====================================================================

To support RFC 4648 we need to add support for base 32 encoding with extended hex alphabet (see 16995). Check also that RFC 4648 test vectors are used in the module tests.
History
Date User Action Args
2019-04-23 18:25:23serhiy.storchakasetrecipients: + serhiy.storchaka, docs@python, paulehoffman
2019-04-23 18:25:22serhiy.storchakasetmessageid: <1556043922.99.0.58094619179.issue36700@roundup.psfhosted.org>
2019-04-23 18:25:22serhiy.storchakalinkissue36700 messages
2019-04-23 18:25:22serhiy.storchakacreate