SIGSEGV on gpg 1.2.1 (was: Re: A GnuPG oddity (decompression))

[David Shaw]

--rS8CxjVDS/+yyDmU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 08, 2003 at 09:49:44AM +0200, Adrian 'Dagurashibanipal' von Bid=
der wrote:
> begin console-log.txt
> vbi@altfrangg:~$ gpg < blah
> gpg: CAST5 encrypted data
>=20
> gpg: Segmentation fault caught ... exiting
> Segmentation fault
> vbi@altfrangg:~$ gpg --decrypt < blah
> gpg: CAST5 encrypted data
>=20
> gpg: Segmentation fault caught ... exiting
> Segmentation fault
> vbi@altfrangg:~$
> end console-log.txt
>=20
> gnupg is 1.2.1-2 package from Debian. Are there interactions with gpg-age=
nt=20
> (using gpgsm 0.9.4-0woody2 Debian packages done by Ralf Nolden)?

That is a known bug with 1.2.1, symmetrically encrypted data, and
gpg-agent.  It is fixed in 1.2.2.

David

--rS8CxjVDS/+yyDmU
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2rc1 (GNU/Linux)
Comment: http://www.jabberwocky.com/david/keys.asc

iD8DBQE+kuVw4mZch0nhy8kRAjXTAJ9/3WJYMAcvLMLCxdLOb1r5gb4GmgCcC+v7
Oxb0Cs3cySH2Ck8LbykPqyo=
=ahg8
-----END PGP SIGNATURE-----

--rS8CxjVDS/+yyDmU--