On 2025-08-30 21:28:32+0800, Guan-Chun Wu wrote: > Previously, fscrypt_base64url_encode() processed input one byte at a > time, using a bitstream, accumulating bits and emitting characters when > 6 bits were available. This was correct but added extra computation.
Can't the custom base64 implementations in fs/ not pass a custom table and padding to the generic algorithm in lib/? Then we only need to maintain this code once. Thomas
