Ohhhhh jeeeee bug persists!
Sat Feb 15 04:00:02 2003
Content-Type: text/plain; charset=us-ascii
After having lost my old key -- just clobbered it, i don't know! --
and generated a new one, and told mutt to only try to use that one,
I'm still getting some of the previous errors.
I recently encrypted a message to some people, and when I looked
through my sent-mail box and tried to read it, I got an empty body and
the following pgp output:
[-- PGP output follows (current time: Fri 14 Feb 2003 09:55:25 PM EST) --]
gpg: Ohhhh jeeee: ... this is a bug (getkey.c:2151:lookup)
secmem usage: 1696/1696 bytes in 4/4 blocks of pool 1696/16384
i can't read it at all. Is pgp thinking it's using my old key
somehow? or is this legitimately a bug in gpg?? i'm using gnupg
1.2.0-1, the deb package current in all debian versions right now, if
i'm not mistaken.
has anyone seen this? it's really confusing!
.~. nori @ sccs.swarthmore.edu=20
// \\ @ maenad.net
/( )\ www.maenad.net
pgp servers broken: get my (*new*) key here:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
-----END PGP SIGNATURE-----