Actions
Bug #6964
closedbase64: consumed bytes are incorrectly set for different modes
Affected Versions:
Effort:
Difficulty:
Label:
Description
For example, given a string 0YPhA d H
and an ample buffer size, consumed bytes should be 4 in RFC2045 mode as there are only 3 valid bytes post 0YPh
and that isn't enough to decode. Actually, looking further, it seems we want to decode all the bytes that we can as long as there is ample destination space but only for RFC 4648.
Actions