struggling with potential keyid conflicts

[John Clizbe]

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

Jim Hurd wrote:

> GPG seems to handle keyid conflicts very awkwardly.
>
> I was playing a bit with the 0xDEADBEEF id (famously conflicted keyid).
>
>
> recv-keys downloads multiple keys with the same key id, but gpg only
> uses the "first" one (I don't know the definition of first, maybe it
> is date?). The only way to access the second (assume for the moment that
> user id's are identical, or also conflicted in a different way) seems to
> be to delete the one I don't want, then sign the one I do want.

I think it's affected by the order they get stored into the keyring. I've
noticed that when doing a refresh, keys are processed in the reverse order
they were added.

You can select individual 0xDEADBEEF keys by specifying the long keyid:
0xF87A2B53DEADBEEF Preston Wilson
0x7AC13FB2DEADBEEF Imad R. Faid 04/28/1999
0xA2061199DEADBEEF Imad R. Faid 08/03/1999

- --
John P. Clizbe                   Inet:   JPClizbe(a)comcast DOT nyet
Golden Bear Networks             PGP/GPG KeyID: 0x608D2A10
  "Most men take the straight and narrow. A few take the road less
traveled.  I chose to cut through the woods."

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Comment: Annoy John Asscraft -- Use Strong Encyption

iD8DBQFAFoZdHQSsSmCNKhARApz5AKDQ9f3ooRtgGaJJOv/n8Xho4W/JcACgh6lz
TKY5gGI3xu+i1VVSd5eMjAU=
=OSaI
-----END PGP SIGNATURE-----