Message309454
I wrote an incremental base-64 decoder for the "codecs" module in Issue 27799, which you could use. It just does some preprocessing using a regular expression to pick four-character chunks before passing the data to a2b_base64. Or maybe implementing it properly in the "binascii" module is better.
Quickly reading RFC 2045, I saw it says "All line breaks or other characters not found in Table 1 [64 alphabet characters plus padding character] must be ignored by decoding software." So this is a real bug, although I think a base-64 encoder that triggers it would be rare. |
|
Date |
User |
Action |
Args |
2018-01-04 03:44:16 | martin.panter | set | recipients:
+ martin.panter, gregory.p.smith, r.david.murray |
2018-01-04 03:44:16 | martin.panter | set | messageid: <1515037456.67.0.467229070634.issue32491@psf.upfronthosting.co.za> |
2018-01-04 03:44:16 | martin.panter | link | issue32491 messages |
2018-01-04 03:44:15 | martin.panter | create | |
|