Re: [netconf] base64encodedvalue== is an invalid base64 value

[Kent Watsen <[e-mail]>]

>> Who cares whether this value roundtrips in an examples??
> 
> I’d expect at least some decent implementations will check for RFC 4648’s mandate "These pad bits MUST be set to
>   zero by conforming encoders”, just like some check for the right number of equals signs.
> Examples that fail in decent implementations are suboptimal.
> (They might even be used in arguments to claim that this decency needs to be removed.)



`base64` doesn’t produce a warning:

    $ echo "base64encodedvalue==" | base64 -d | base64
    base64encodedvaluQ==



`openssl` doesn’t produce a warning:

    $ echo "base64encodedvalue==" | openssl enc -d -base64 -A | openssl enc -base64 -A
    base64encodedvaluQ==



Python doesn’t produce a warning:

    $ printf "import binascii\nprint(binascii.b2a_base64(binascii.a2b_base64('base64encodedvalue=='), newline=False).decode('ascii'))" |  python -
    base64encodedvaluQ==