Hi,
On Thu, Nov 21, 2019 at 12:04:11PM +0530, vardhaman narasagoudar wrote:
> On Thu, Nov 21, 2019 at 12:51 AM Paul Eggert wrote:
> > On 11/20/19 6:22 AM, Martin Schulte wrote:
> > > vardhamanbn1 is a valid encoding
> >
> > Thanks for explaining; closing the bug report.
>
> Thanks for replying
Hi Team,
Thanks for replying the query, but if I check online (
https://www.base64decode.org/) for decoding the same in online .
I get an error message (which is valid) e.g:-
1) if I try to decode "99" I get an error message
"No printable characters found, try another source charset,
On 11/20/19 6:22 AM, Martin Schulte wrote:
vardhamanbn1 is a valid encoding
Thanks for explaining; closing the bug report.
Hello Vardhaman!
> 3) Now trying to decode a non-encoded value of 12characters
> [vardhaman@oc6085028360 ~]$ echo 'vardhamanbn1' | base64 --decode
> ��݅�[vardhaman@oc6085028360 ~]$ echo $?
> 0
$ echo -n $'\275\252\335\205\251\232\235\271\365' | base64
vardhamanbn1
So, vardhamanbn1 is a
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
99
[vardhaman@oc6085028360 ~]$