bug#66265: closed (Make padding optional with base64)

[GNU bug Tracking System]

Your message dated Sat, 7 Oct 2023 15:00:31 +0100
with message-id <f4af6f20-62b4-05cd-9fd2-a76fbd492dec@draigBrady.com>
and subject line Re: bug#66265: Make padding optional with base64
has caused the debbugs.gnu.org bug report #66265,
regarding Make padding optional with base64
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
66265: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66265
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Make padding optional with base64
>
>
>
>
> Date: 
>
> Fri, 29 Sep 2023 11:46:18 +0200
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
>
>
>
>
> Hi,
>
> RFC 4648 says[1]:
> >   In some circumstances, the use of padding ("=") in base-encoded data
> >   is not required or used.
>
> Currently, the 'base64' application always includes the padding when 
> encoding, and prints an warning/error message (on stderr) if padding is 
> omitted when decoding.  Decoding is nonetheless successful (the correct 
> data is emitted on stdout) if the base64-encoded data omits the padding.
>
> I think the base64 application should be updated to support 
> base64-encoded data without padding.
>
> My suggestion would be to add an option to base64 to control whether 
> padding is added when encoding.  For decoding, it might make sense to 
> add an option to control whether padding is expected.
>
> (although, other approaches might be possible)
>
> Cheers,
> Paul.
>
> [1] https://datatracker.ietf.org/doc/html/rfc4648#section-3.2
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#66265: Make padding optional with base64
>
>
>
>
> Date: 
>
> Sat, 7 Oct 2023 15:00:31 +0100
>
>
>
>
> User-agent: 
>
> Mozilla Thunderbird
>
>
>
>
> Pushed.
>
> Marking this as done.
>
> cheers,
> Pádraig
>
>
> --- End Message ---