Mailing List Archive

Should this happen?
Using gpg -d to decode a PGP6 encoded file:

% gpg -d ~/categ2.xls.asc >categ2.xls
gpg (GnuPG) 0.4.5; Copyright (C) 1998 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.


You need a passphrase to unlock the secret key for
user: "Edd Dumbill <edd@heddley.com>"
(2048-bit ELG-E key, ID 98697FCC, created 1998-08-08)

gpg: iobuf-5.3: clear_eof 'decode_filter' with enabled filter
gpg: iobuf-5.3: clear_eof 'decode_filter' with no EOF pending

gpg: Ohhhh jeeee: Ohh jeee, trying to remove an intermediate filter
secmem usage: 1632/3296 bytes in 4/8 blocks of pool 3904/16384
IOT trap/Abort


The file appears to be fine -- but this hardy seems a graceful
exit! This happens for gpg 0.4.5 and 0.9. My main key is one
imported from PGP5. Here's a backtrace from gpg 0.9:

#0 0x4008e8d1 in __kill ()
#1 0x4005d6d9 in raise (sig=135027726)
#2 0x80b333a in iobuf_pop_filter (a=0x80ceffc, f=0, ov=0x0) at iobuf.c:783
#3 0x80b3733 in iobuf_clear_eof (a=0x80ceffc) at iobuf.c:878
#4 0x8083bdc in decrypt_data (ed=0x80d210c, dek=0x40008588) at encr-data.c:107
#5 0x8060239 in proc_encrypted (c=0x80cec64, pkt=0x80cf48c) at mainproc.c:222
#6 0x8061ced in do_proc_packets (c=0x80cec64, a=0x80ceffc) at mainproc.c:760
#7 0x806193a in proc_encryption_packets (a=0x80ceffc) at mainproc.c:701
#8 0x80877ff in decrypt_message (filename=0xbffff597 "/home/pingu/edmundd/categ2.xls.asc") at decrypt.c:74
#9 0x8051e67 in main (argc=1, argv=0xbffff3d4) at g10.c:1009
#10 0x804f49e in _start ()

regards

--
Edd Dumbill -- edd@heddley.com -- http://www.heddley.com/edd/
PGP key available at -- http://www.heddley.com/edd/pubkey.asc
5B D5 8E 66 D4 43 D7 C0 CF 55 BD 4A B2 0F 89 18 BA F5 0C 04
Re: Should this happen? [ In reply to ]
Edd Dumbill <edmundd@heddley.com> writes:

> The file appears to be fine -- but this hardy seems a graceful
> exit! This happens for gpg 0.4.5 and 0.9. My main key is one
> imported from PGP5. Here's a backtrace from gpg 0.9:

I fixed this bug today but a I have to fix some other things
too; maybe I can release something tomorrow.

Werner