bug#66698: closed (I think hex decoding with basenc -d --base16 should be case-insensitive)

[GNU bug Tracking System]

Your message dated Mon, 23 Oct 2023 13:01:17 +0100
with message-id <9cb30d1b-3f3d-5d3a-59ab-5ee630ea633f@draigBrady.com>
and subject line Re: bug#66698: I think hex decoding with basenc -d --base16 
should be case-insensitive
has caused the debbugs.gnu.org bug report #66698,
regarding I think hex decoding with basenc -d --base16 should be 
case-insensitive
to be marked as done.

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


-- 
66698: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66698
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> I think hex decoding with basenc -d --base16 should be case-insensitive
>
>
>
>
> Date: 
>
> Mon, 23 Oct 2023 11:37:36 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.2 (berkeley-unix)
>
>
>
>
> Hi,
>
> the docs for basenc --base16 says "hex encoding (RFC4648 section 8)".
> The referenced section in that RFC says 
>
>   Essentially, Base 16 encoding is the standard case-insensitive hex
>   encoding and may be referred to as "base16" or "hex".
>
> I think it would be both more useful, and consistent with docs, if
> basenc -d --base16 accepted either upper- or lowercase hex digits.
>
> Current behavior, with basenc (GNU coreutils) 9.1:
>
>   $ echo 666F6F0A |basenc --base16 -d
>   foo
>   $ echo 666F6f0A |basenc --base16 -d
>   fobasenc: invalid input
>
> I think both inputs should give the same output, "foo\n", at least by
> default. Possibly configurable with options like --strict, --upper,
> --lower, etc (--upper/--lower would be useful also for the --base16
> encoding, i.e., no -d).
>
> Regards,
> /Niels
>
> -- 
> Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677.
> Internet email is subject to wholesale government surveillance.
>
>
>
>
> --- End Message ---

--- Begin Message --- Subject: Re: bug#66698: I think hex decoding with basenc -d --base16 should be case-insensitive Date: Mon, 23 Oct 2023 13:01:17 +0100 User-agent: Mozilla Thunderbird

On 23/10/2023 10:37, Niels Möller wrote:

Hi,

the docs for basenc --base16 says "hex encoding (RFC4648 section 8)".
The referenced section in that RFC says

   Essentially, Base 16 encoding is the standard case-insensitive hex
   encoding and may be referred to as "base16" or "hex".

I think it would be both more useful, and consistent with docs, if
basenc -d --base16 accepted either upper- or lowercase hex digits.

Current behavior, with basenc (GNU coreutils) 9.1:

   $ echo 666F6F0A |basenc --base16 -d
   foo
   $ echo 666F6f0A |basenc --base16 -d
   fobasenc: invalid input

I think both inputs should give the same output, "foo\n", at least by
default. Possibly configurable with options like --strict, --upper,
--lower, etc (--upper/--lower would be useful also for the --base16
encoding, i.e., no -d).

Agreed.
Will apply the attached later.
Marking this as done.

thanks,
Pádraig

basenc-lower-hex.patch
Description: Text Data

--- End Message ---