Bus Error on certain keys [Patch provided]

[Jack Repenning]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, June 8, 2004, at 05:05  AM, David Shaw wrote:

> I see what the problem is, but I'm baffled as how you made that key.
> The problem is that the key is a secret key with public subkeys.
> There is no such thing.  Of course, GnuPG shouldn't bus error on it,
> but at the same time, this key is likely corrupt.

Huh.  Fairly new key, too (I have keys reaching back to PGP 2.1...).

> What happens when you try this with the 1.2.5 release candidate?

Sorry, I'm new around here, how do I do that?  I looked around a bit, 
but couldn't find an RC tarball.  I assume I should check out tag 
RC-1-2-5rc1?  I speak fairly fluent CVS, and found advice at 
www.gnupg.org on fetching the sources via anoncvs, but I get server 
connection refusals (which, I suppose, might mean "too busy," or 
"temporary server problems," or might mean "I need to negotiate with 
someone to add my from-host to an access list"):

 > cvs -d :pserver:anoncvs at cvs.gnupg.org:/cvs/gnupg login
(Logging in to anoncvs at cvs.gnupg.org)
CVS password:
cvs [login aborted]: connect to cvs.gnupg.org:2401 failed: Connection 
refused





<><
Jack Repenning
<mailto:jack at netgate.net>

186,262 miles per second -- Not just a good idea ... it's the LAW!!!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: GPG-encrypted email preferred

iD8DBQFAxpMpUfE+7TuC6HARAr4bAJsFbY18JZ75q+3hLSBMfUQB717wiQCfcxSq
I8X965FousuVUzjzJGEyiQs=
=CDZy
-----END PGP SIGNATURE-----