On 27/02/2023 15.24, Carsten Bormann wrote:
On 2023-02-27, at 15:04, Ladislav Lhotka<[email protected]> wrote:
Unlike non-alphabet characters, RFC 4648 doesn't say that such a character in
encoded data is invalid.
Not explicitly, but it also gives you an algorithm for arriving at the encoded
value that never can result in the characters that I consider invalid [1]:
When fewer than 24 input
bits are available in an input group, bits with value zero are added
(on the right) to form an integral number of 6-bit groups.
Note the explicit “with value zero”.
FWIW, my implementation (Yangson) uses Python standard library base64 that
accepts it without complaints even with validation turned on:
import base64
base64.b64decode("ue==", validate=True)
b'\xb9'
So I assume the authors consider this input valid, and I saw no reason to be
concerned about it.
Thank you — that was the kind of input I was looking for.
Now what do other implementations do?
OpenDaylight uses plain Java, which in turn boils down to:
| Welcome to JShell -- Version 17.0.6
| For an introduction type: /help intro
jshell> java.util.Base64.getDecoder().decode("ue==")
$1 ==> byte[1] { -71 }
Regards,
Robert
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
