zlacker

[return to "How fast can browsers process base64 data?"]
1. danhau+Fd[view] [source] 2025-11-29 10:49:12
>>mfigui+(OP)
> However, when decoding, we must handle errors and skip spaces.

This had me scratching my head. Why would a base64 decoder need to skip spaces? But indeed, MDN documents this behavior:

> Note that: The whitespace in the space is ignored.

JS never ceases to surprise. Also, check out that typo :D

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

◧◩
2. clucki+Io[view] [source] 2025-11-29 13:12:21
>>danhau+Fd
So technically it’s now possible to hide a payload in somewhat human-readable text, as long as it base64-decodes.
◧◩◪
3. recurs+yIl[view] [source] 2025-12-06 00:27:10
>>clucki+Io
Now? There's no change. Also human readable text substantially consists of letters. But that's most of the base64 alphabet too. So this isn't like steganography. All the letters in the human-readable words are valid base64 characters too. The only thing about this is that you get to choose where to put the spaces and newlines. You can't exactly construct arbitrary payloads starting from arbitrary messages.
[go to top]