GNU logs - #37992, boring messages

Message sent to bug-coreutils@HIDDEN:

Subject: bug#37992: Base64 decode should ignore CRLF
Resent-From: Steven Hilton <malvidin@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-coreutils@HIDDEN
Resent-Date: Wed, 30 Oct 2019 14:33:02 +0000
Resent-Message-ID: <handler.37992.B.157244598127264 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 37992 <at> debbugs.gnu.org
MIME-Version: 1.0
From: Steven Hilton <malvidin@HIDDEN>
Date: Wed, 30 Oct 2019 15:25:16 +0100
Message-ID: <CAD1nBbLhEi3gXVOi5o_=cffytZJdLn7Mn91GGR+4=mJRw92CeA@HIDDEN>
Content-Type: multipart/alternative; boundary="00000000000081d24c0596218b31"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--00000000000081d24c0596218b31
Content-Type: text/plain; charset="UTF-8"

I believe that the base64 implementation in coreutils should ignore
carriage return and line feed line endings (CR, LF, CRLF). Currently, it
only ignores LF line endings.
The -i/--ignore-garbage flag is effective, but should not fail on common
line endings.

$ echo -ne
"R05VIEJhc2U2NCBkZWNvZGUgc2hvdWxkIGlnbm9yZSBib3RoIENSIGFuZC9vciBMRg0K\r\nR05VIEJhc2U2NCBkZWNvZGUgc2hvdWxkIGlnbm9yZSBib3RoIENSIGFuZC9vciBMRg0K"
| base64 -d
Current Output:
GNU Base64 decode should ignore both CR and/or LF
base64: invalid input

Expected Output:
GNU Base64 decode should ignore both CR and/or LF
GNU Base64 decode should ignore both CR and/or LF

Per the Base64 RFC, section 3.3,

Note that this means that any adjacent carriage return/line feed
(CRLF) characters constitute "non-alphabet characters" and are
ignored.

https://tools.ietf.org/html/rfc4648#section-3.3
<https://www.google.com/url?q=https://tools.ietf.org/html/rfc4648%23section-3.3&sa=D&source=hangouts&ust=1572513581650000&usg=AFQjCNGmIlJSlyucb75tnWNUbAovfdasIg>

My interpretation of this section is that the base64 decoding should either
fail on any non-Alphabet character, or should ignore any line ending
combination.

--00000000000081d24c0596218b31
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style=3D"vertical-align:top;padding:7px 0px 1px;borde=
r-radius:5px 0px 5px 5px;color:rgb(38,38,38);font-size:13px"><div id=3D"m_1=
882433811314112529gmail-:91.co" style=3D"color:rgb(38,50,56)"><div id=3D"m_=
1882433811314112529gmail-:93.ma" style=3D"line-height:16px;margin-bottom:6p=
x;margin-left:9px;margin-right:9px;opacity:1;word-break:break-word"><font f=
ace=3D"arial, sans-serif">I believe=C2=A0that the base64 implementation in =
coreutils should ignore carriage return and line feed line endings (CR, LF,=
 CRLF). Currently, it only ignores LF line endings.</font></div><div id=3D"=
m_1882433811314112529gmail-:93.ma" style=3D"line-height:16px;margin-bottom:=
6px;margin-left:9px;margin-right:9px;opacity:1;word-break:break-word"><font=
 face=3D"arial, sans-serif">The -i/--ignore-garbage flag is effective, but =
should not fail on common line endings.=C2=A0</font></div><div id=3D"m_1882=
433811314112529gmail-:93.ma" style=3D"line-height:16px;margin-bottom:6px;ma=
rgin-left:9px;margin-right:9px;opacity:1;word-break:break-word"><font face=
=3D"arial, sans-serif"><br></font><font face=3D"monospace">$ echo -ne &quot=
;R05VIEJhc2U2NCBkZWNvZGUgc2hvdWxkIGlnbm9yZSBib3RoIENSIGFuZC9vciBMRg0K\r\nR0=
5VIEJhc2U2NCBkZWNvZGUgc2hvdWxkIGlnbm9yZSBib3RoIENSIGFuZC9vciBMRg0K&quot; | =
base64 -d<br></font><font face=3D"Roboto, Arial, sans-serif">Current Output=
:</font><br><font face=3D"monospace">GNU Base64 decode should ignore both C=
R and/or LF<br>base64: invalid input<br></font><br><font face=3D"Roboto, Ar=
ial, sans-serif">Expected Output:</font><br><font face=3D"monospace">GNU Ba=
se64 decode should ignore both CR and/or LF<br>GNU Base64 decode should ign=
ore both CR and/or LF<br></font></div><div id=3D"m_1882433811314112529gmail=
-:93.ma" style=3D"font-family:Roboto,Arial,sans-serif;line-height:16px;marg=
in-bottom:6px;margin-left:9px;margin-right:9px;opacity:1;word-break:break-w=
ord"><br></div><div id=3D"m_1882433811314112529gmail-:93.ma" style=3D"font-=
family:Roboto,Arial,sans-serif;line-height:16px;margin-bottom:6px;margin-le=
ft:9px;margin-right:9px;opacity:1;word-break:break-word">Per the Base64 RFC=
, section 3.3,=C2=A0</div><div id=3D"m_1882433811314112529gmail-:93.ma" sty=
le=3D"line-height:16px;margin-bottom:6px;margin-left:9px;margin-right:9px;o=
pacity:1;word-break:break-word"><pre style=3D"font-size:13.3333px;margin-to=
p:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">Note that this =
means that any adjacent carriage return/line feed (CRLF) characters constit=
ute &quot;non-alphabet characters&quot; and are ignored.</pre></div><div id=
=3D"m_1882433811314112529gmail-:93.ma" style=3D"font-family:Roboto,Arial,sa=
ns-serif;line-height:16px;margin-bottom:6px;margin-left:9px;margin-right:9p=
x;opacity:1;word-break:break-word"><span id=3D"m_1882433811314112529gmail-:=
93.co" dir=3D"ltr"><a rel=3D"nofollow noreferrer noopener" href=3D"https://=
www.google.com/url?q=3Dhttps://tools.ietf.org/html/rfc4648%23section-3.3&am=
p;sa=3DD&amp;source=3Dhangouts&amp;ust=3D1572513581650000&amp;usg=3DAFQjCNG=
mIlJSlyucb75tnWNUbAovfdasIg" dir=3D"ltr" style=3D"unicode-bidi:isolate;colo=
r:rgb(38,50,56)" target=3D"_blank">https://tools.ietf.org/html/rfc4648#sect=
ion-3.3</a></span></div><div id=3D"m_1882433811314112529gmail-:93.ma" style=
=3D"font-family:Roboto,Arial,sans-serif;line-height:16px;margin-bottom:6px;=
margin-left:9px;margin-right:9px;opacity:1;word-break:break-word"><br></div=
><div id=3D"m_1882433811314112529gmail-:93.ma" style=3D"font-family:Roboto,=
Arial,sans-serif;line-height:16px;margin-bottom:6px;margin-left:9px;margin-=
right:9px;opacity:1;word-break:break-word">My interpretation of this sectio=
n is that the base64 decoding should either fail on any non-Alphabet charac=
ter, or should ignore any line ending combination.</div></div></div></div>

--00000000000081d24c0596218b31--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Steven Hilton <malvidin@HIDDEN>
Subject: bug#37992: Acknowledgement (Base64 decode should ignore CRLF)
Message-ID: <handler.37992.B.157244598127264.ack <at> debbugs.gnu.org>
References: <CAD1nBbLhEi3gXVOi5o_=cffytZJdLn7Mn91GGR+4=mJRw92CeA@HIDDEN>
X-Gnu-PR-Message: ack 37992
X-Gnu-PR-Package: coreutils
Reply-To: 37992 <at> debbugs.gnu.org
Date: Wed, 30 Oct 2019 14:33:03 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-coreutils@HIDDEN

If you wish to submit further information on this problem, please
send it to 37992 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
37992: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D37992
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.