[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] Wrong key fetched?
|
From: |
David Shaw |
|
Subject: |
Re: [Sks-devel] Wrong key fetched? |
|
Date: |
Fri, 25 Jan 2013 14:48:09 -0500 |
On Jan 25, 2013, at 2:41 PM, Christoph Egger <address@hidden> wrote:
> John Clizbe <address@hidden> writes:
>> Christoph Egger wrote:
>>> Something weird happening when fetching 0xE33EC6CCCC3DF983 -- it gets
>>> 0x9CDF568F which doesn't even have a subkey called 0xE33EC6CCCC3DF983 as
>>> far as I can see. Anyone knows what's going on?
>>>
>>> Regards
>>>
>>> Christoph
>>>
>> It's a subkey according to a verbose index...
>> http://keyserver.gingerbear.net:11371/pks/lookup?search=0xE33EC6CCCC3DF983&fingerprint=on&op=vindex
>
> Hm now that makes me wonder by the subkey is not displayed by gpg
> --fingerprint while it does show all different subkeys on my key
The subkey binding signature is invalid, so GPG is removing the subkey. Do the
import with '-v':
gpg: key 9CDF568F: invalid subkey binding
gpg: key 9CDF568F: skipped subkey
David