[Belenios-discuss] Which BASE64()?

[Julien Moutinho <julm+inria AT autogeree.net>]

Hi belenios-discuss@,

In section "4.12 Ballots" of the 1.6 specification of Helios-C,
a BASE64() function is mentioned,
one would expect it to be the base64 encoding of RFC4648.
But currently Belenios uses Cryptokit.Base64.encode_compact
> Same as Cryptokit.Base64.encode_multiline, but the output is not
> split into lines, and no final padding is added.
> This is adequate for encoding short strings for transmission
> as part of URLs, for instance.
Source: /usr/share/doc/libcryptokit-ocaml-dev/cryptokit/Cryptokit.Base64.html

And AFAICS encode_compact is not exactly the same as RFC4648's base64,
which requires padding by default:
> 3.2.  Padding of Encoded Data
> 
>    In some circumstances, the use of padding ("=") in base-encoded data
>    is not required or used.  In the general case, when assumptions about
>    the size of transported data cannot be made, padding is required to
>    yield correct decoded data.
> 
>    Implementations MUST include appropriate pad characters at the end of
>    encoded data unless the specification referring to this document
>    explicitly states otherwise.
Source: https://tools.ietf.org/rfc/rfc4648

Could Belenios use encode_compact_pad?

Regards,
Julien Moutinho

Attachment: signature.asc
Description: PGP signature