[pkg-gnupg-maint] Bug#907234: gnupg warns that an email was signed by a key that expired... in 2018

[Nicolas Braud-Santoni]

Control: retitle -1 gnupg should correctly deal with multiple keyrings

Hi Alexandre,

Thanks for finding this mail on gnupg-users; it was indeed that my public
keyring didn't have your updated key (with the new subkey expiration).

The second entry was from /usr/share/keyrings/debian-keyring.gpg, which was
more up-to-date.


Best,

  nicoo

On Fri, Aug 24, 2018 at 09:59:12PM -0400, Alexandre Viau wrote:
> On 2018-08-24 09:54 PM, Alexandre Viau wrote:
> > It looks like the signature should be accepted and that there should not
> > be two entries for 0xDA82830E3CCC3A3A, as they are the same key. Am I
> > missing something?
> 
> This might be relevant:
>  - https://lists.gnupg.org/pipermail/gnupg-users/2004-January/021284.html
> 
> [[
> 
> > The second key correspond to a previous state of my key (before I
> > added the second encryption key 1CF0D39E).
> >
> > Shouldn't the keyring merge these two keys ?
> 
> No, if you have a keyring with a duplicate key, the merge happens on
> import.  Since the keys are already there, the way to fix it is:
> 
> * export both keys to a file
> * delete the keys on the keyring.
> * import the keys again.  They will be merged.
> 
> Make a backup first, just in case
> 
> ]]
> 
> Cheers,
> 
> -- 
> Alexandre Viau
> aviau at debian.org
> 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20180826/9557cc06/attachment.sig>