One more segfault with gpg-1.0.1

Jan-Benedict Glaw jbglaw@lug-owl.de
Fri, 28 Apr 2000 14:13:58 +0200


--lrZ03NoBR/3+SXJZ
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi!

I hit one more bug these days;) Currently I'm working on putting together
a key management tool (read: frontend) because I can't find anything really
*good*. gpgp and seahorse are nice, but they aim a user's interface for
encryption/decryption/verification. But okay, here is what I tested:

(0xKKKK is a test key on a non-networking machine;)

gpg --with-colons --with-key-data --list-secret-keys 0xKKKKK

GnuPG writes the first line (sec:u:1024.....) and then dies...

gdb then shows the buggy line:

0x807c2cf in print_key_data (pk=3D0x0, keyid=3D0xKKKKK) at keylist.c:148
148         int n =3D pubkey_get_npkey( pk->pubkey_algo );

(gdb) bt
#0  0x807c2cf in print_key_data (pk=3D0x0, keyid=3D0xbffffb00) at keylist.c=
:148
                                    ^^^--- A nice NULL pointer;)
#1  0x807c795 in list_keyblock (keyblock=3D0x80c7658, secret=3D1) at keylis=
t.c:272
#2  0x807c20b in list_one (names=3D0x80c4f60, secret=3D1) at keylist.c:125
#3  0x807c03b in secret_key_list (list=3D0x80c4f60) at keylist.c:63
#4  0x8052da8 in main (argc=3D0, argv=3D0xbffffd58) at g10.c:1200

Please don't flame me for using more-or-less insecure ways of retreiving
key data -- the program shall run off a self-booting CDROM;)

MfG, JBG

--=20
Fehler eingestehen, Gr=F6=DFe zeigen: Nehmt die Rechtschreibreform zur=FCck=
!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=3D0x8399E1BB fingerprint=3D250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 83=
99 E1BB

--lrZ03NoBR/3+SXJZ
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEAREBAAYFAjkJgIYACgkQHb1edYOZ4bsFfACffUG/WFXx7msgJsLdPVTKQ+BF
oq8AoIoa1d/+W5VXogJYIZNj/2zvWzk/
=/NSM
-----END PGP SIGNATURE-----

--lrZ03NoBR/3+SXJZ--