Re: [LUG] More on GPG

[Mike Callaghan <mike@xxxxxxxxxxxxxxxxxxxx>]

Neil wrote: 
> The reason is here:
> Evolution signs with this key:
> [neil@xxxxx neil]$ gpg --list-sigs 8d86b65e
> pub  1024D/8D86B65E 2003-02-28 Michael D Callaghan
> <mike@xxxxxxxxxxxxxxxxxxxx>
> sig    8D86B65E 2003-02-28   Michael D Callaghan
> <mike@xxxxxxxxxxxxxxxxxxxx>
> sub  2048g/6EFE80D9 2003-02-28
> sig    8D86B65E 2003-02-28   Michael D Callaghan
> <mike@xxxxxxxxxxxxxxxxxxxx>
<snip> 
> > I am particularly puzzled by the 'WARNING' as I have signed the key
> > myself. My own key, not surprisingly, is trusted.
> 
> Locally? It certainly hasn't made it to the keyserver yet. If you sign
> 8d86b65e with 2801834d and set the trust in keys signed by 2801834d to
> full,
> you should find that my key becomes fully trusted again.
All becomes clear now. I thought I had resigned Neil's key with my new
key (8D86B65E) but had in fact used one (E5A62DD0) I had generated while
playing with gpg on the laptop. 

8D86B65E is my new key and is now set as default on both Windows and
Linux systems. I have re-signed those keys previously signed with
2801834D. 

2801834D has been revoked. Keyservers have been updated for both keys.

Thanks for the guidance. 

-- 
Mike Callaghan
Cornwall
gpg fingerprint: 52C0 1F95 EAF0 3736 D8E0  5F59 E214 5779 8D86 B65E

Attachment: signature.asc
Description: This is a digitally signed message part