struggling with potential keyid conflicts

David Shaw dshaw at jabberwocky.com
Tue Jan 27 17:10:06 CET 2004


On Tue, Jan 27, 2004 at 03:54:04PM -0500, Jason Harris wrote:
> On Tue, Jan 27, 2004 at 01:13:54PM -0500, David Shaw wrote:
> > On Tue, Jan 27, 2004 at 11:36:06AM -0500, Jim Hurd wrote:
>  
> > > Do you know where keyservers are with this issue? I tried:
> > > 
> > > gpg --keyserver pgp.mit.edu --recv-key  0x5BD18B6A42B9247EF79214B7F87A2B53DEADBEEF
> > > 
> > > And it gives the same result as
> > > 
> > > gpg --keyserver pgp.mit.edu --recv-key  0xDEADBEEF
> 
> > It's the keyserver.  GnuPG gives the whole fingerprint to the
> > keyserver, and the keyserver handles it as it sees fit (which
> > generally means to truncate it to the lowest 32 bits).
> 
> :)  hkp:// URLs are still using the short keyids:
> 
> %gpg --version
> gpg (GnuPG) 1.2.4

Oops.

$ gpg --version
gpg (GnuPG) 1.3.5-cvs

There have been dozens of improvements between 1.2 and 1.3.  I forget
which version I'm running sometimes.

So, upgrade for that feature. ;)

David



More information about the Gnupg-users mailing list