bug#38299: closed (A bug while trying to decode a non encode base64)

[GNU bug Tracking System]

Your message dated Wed, 20 Nov 2019 11:21:39 -0800
with message-id <address@hidden>
and subject line Re: bug#38299: A bug while trying to decode a non encode base64
has caused the debbugs.gnu.org bug report #38299,
regarding A bug while trying to decode a non encode base64
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
38299: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38299
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: A bug while trying to decode a non encode base64 Date: Wed, 20 Nov 2019 16:46:45 +0530

Hi Team,

Looks like there is a bug while trying to decode a non-encode base64 for 12 characters (or multiple of 12) , the return code is always 0.

e.g:- 

1) When trying to decode a encoded value

[vardhaman@oc6085028360 ~]$ echo  'Nzc3Nzk5Cg==' | base64 --decode
777799
[vardhaman@oc6085028360 ~]$ echo $?
0

2)   A sample when trying to decode a non-encode value 

[vardhaman@oc6085028360 ~]$ echo  '777799' | base64 --decode

����base64: invalid input
[vardhaman@oc6085028360 ~]$ echo $?
1

3) Now trying to decode a non-encoded value of 12characters

[vardhaman@oc6085028360 ~]$ echo  'vardhamanbn1' | base64 --decode
��݅�����[vardhaman@oc6085028360 ~]$ echo $?
0

The point 3 should return code as 1 , as invalid input

I feel this bug is present in all version , anywhere sharing the current version where I tested

vardhaman@oc6085028360 ~]$ base64 --version
base64 (GNU coreutils) 8.22
Copyright (C) 2013 Free Software Foundation, Inc.

--

Thanks & Regards
Vardhaman B.N
9945840928

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#38299: A bug while trying to decode a non encode base64
>
>
>
>
> Date: 
>
> Wed, 20 Nov 2019 11:21:39 -0800
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
>
>
>
>
> On 11/20/19 6:22 AM, Martin Schulte wrote:
> > vardhamanbn1 is a valid encoding
>
> Thanks for explaining; closing the bug report.
>
>
> --- End Message ---