On 25.07.2018 05:52, Christos Zoulas wrote: > In article <20180724185738.ga15...@britannica.bec.de>, > Joerg Sonnenberger <jo...@bec.de> wrote: >> >> Why do we need another base64 encoder/decoder? > > So I've been looking into how to get rid of it and re-use uuencode > uudecode for it and it is proving difficult. I am trying to provide > a command line compatible utility with the "base64" command from > MacOS/X and Linux: > > - They use a single command to encode and decode (uuencode and decode > are two separate programs). I would have to either write a shell > script front end (and modify them not to output a header) to be > able to emulate that. > - uudecode is using b64_pton() which does not handle arbitrary whitespace. > > I could merge all three into one, but this is more annoying and risky > to break things due to the amount of legacy behavior in the uu commands. > > Any better options? > > christos >
From a fuzzing point of view, it will be possible to attach libFuzzer with 0 ifdefs once the base64 encode/decode routines will be stored in files without main().
signature.asc
Description: OpenPGP digital signature
