Any word on the bug?

[David Shaw]

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

On Tue, Jun 24, 2003 at 11:58:17PM -0500, Robert J. Hansen wrote:
> >This is not the same problem.  The original problem was that misleading
> 
> Ahh.  Okay, my goof; I thought it was related.
> 
> >going to work via -u.  I'm not quite sure how you got to where you are
> >since GnuPG always adds new user IDs to both the public and secret
> >keys.  Do you have more than one GnuPG installation that you use?
> >They're out of sync.
> 
> Have a GnuPG installation on my laptop and another one on my home box, 
> and I'm forever sshing between the two.  It'd be strange if I somehow 
> morphed keys from one to the other, but I've seen stranger, and most of 
> the stranger things I've been responsible for.

I think that out of sync keyrings is one of those things that (in an
ideal universe) the computer should handle automatically for people.
Given the way OpenPGP keys are specified, the secret key is identical
to the public key (and in fact contains a complete public key) with
the addition of the secret material tacked on.  There is no real
reason why a search for a secret key can't be done on the public
keyring and then check for a matching secret part.  The GnuPG 2.0
prototype does something even more powerful than this, and doesn't
even store the duplicated parts of the secret key.

In such a system, your problem would have never come up since there is
only one place that user IDs exist, so there is nothing for them to be
in sync with.

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3rc1 (GNU/Linux)
Comment: Key available at http://www.jabberwocky.com/david/keys.asc

iD8DBQE++lTy4mZch0nhy8kRAlvkAKCCMq5WFSGzTIadpgCkjCnyTvEyEACfRgVy
MzaKqXEH6jT+EQZ/5pSq9s4=
=tlp8
-----END PGP SIGNATURE-----