Re: segfault in rlog.c

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


() Ray Bellis <[email protected]>
() Wed, 26 Jan 2022 12:23:27 +0000

   [I already added this to the online bug DB as
   http://savannah.gnu.org/bugs/index.php?61932]

Oops, our messages crossed paths.  I responded on savannah, so i
won't repeat myself here.  However, i'll explain further my
thinking: If we go down the =E2=80=98break=E2=80=99 route, then any comma-v=
 file
could carry a (potentially malicious?) payload in that "prior to
last @" region, as long as it doesn't have a SPC character in
it.  That worries me.

=2D-=20
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)               ; (2022) Software Libero
   (pcase (context query)               ;       =3D Dissenso Etico
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
=2D-------------------------------------- 6CE4 6703 2224 4C80 7502


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iG4EARECAC4WIQR0jqDoHLinSJv6bORnAyIkTIB1AgUCYfFMXhAcdHRuQGdudXZv
bGEub3JnAAoJEGcDIiRMgHUC4MgAnRpgGoh22hmrqX/DNFljMAYvf8dLAJ4ooe6p
R+f6aiKguPz6u/2jV+DOdw==
=df4p
-----END PGP SIGNATURE-----
--=-=-=--