[slug] Re: Ohhhh jeeee: ... this is a bug
Sat Mar 29 18:57:02 2003
Content-Type: text/plain; charset=us-ascii
on Thu, 27 Mar 2003 10:54:42AM -0500, David Shaw insinuated:
> On Thu, Mar 27, 2003 at 02:44:05AM -0500, Nori Heikkinen wrote:
> > gpg: Ohhhh jeeee: ... this is a bug (getkey.c:2208:lookup) secmem
> > usage: 1696/1696 bytes in 4/4 blocks of pool 1696/16384
> That error means "I did a lookup for a secret key in the secret
> keyring, and got back a public key. Why is that in there?"
> As strange as it seems, it looks like the same error you had last
> time. Do you have some process running that might be mangling files
> into each other by accident? (a misbehaving backup script, perhaps?)
i really doubt it ... what might be mangling a relevant file? i have
cron jobs running every hour to rsync a couple directories to a remote
system, but not ~/.gnupg ... i daily update an ascii version of my key
by script, but it shouldn't misbehave, afaik!
> Before you do anything, back up your .gnupg directory. If something
> is eating it, best to establish a good copy as soon as possible.
i backed it up as soon as i created this key, so i wouldn't run into
this problem again. but i just restored from backup, and the error
hasn't changed. does this mean that my key was corrupt in some was as
soon as it was created?? that seems *really* weird.
.~. nori @ sccs.swarthmore.edu
// \\ @ maenad.net
/( )\ www.maenad.net
pgp servers finicky: get my (*new*) key here:
(please *remove* old key 11e031f1!)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----