Re: Key corruption: duplicate signatures and usage flags

On Fri, 23 Jun 2017 10:02, madd...@madduck.net said: > Are you saying that gnupg 2.1.18 added the self-signature in the > wrong place? There is no right or wrong place. gpg uses the latest valid self-signature according to the timestamp in the self-signature. Use --with-colons to see the full

Re: Key corruption: duplicate signatures and usage flags

also sprach Werner Koch [2017-06-23 09:40 +0200]: > Those flags are tracked in self-signatures. When changing a flag > a new self-signature is used. This will be uploaded to the > keyserver. gpg uses the flags from the latest self-signature it > has. So how does this explain

Re: Key corruption: duplicate signatures and usage flags

On Fri, 23 Jun 2017 00:33, 2014-667rhzu3dc-lists-gro...@riseup.net said: > I didn't know you could remove a usage flag once the key was on the Those flags are tracked in self-signatures. When changing a flag a new self-signature is used. This will be uploaded to the keyserver. gpg uses the

Re: Key corruption: duplicate signatures and usage flags

also sprach MFPA <2014-667rhzu3dc-lists-gro...@riseup.net> [2017-06-23 00:33 +0200]: > I didn't know you could remove a usage flag once the key was on the > keyservers. Well, it somehow seems to work, apart from the fact that gnupg first needs to clean up the key (using --edit-key) after

Re: Key corruption: duplicate signatures and usage flags

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thursday 22 June 2017 at 12:22:46 PM, in , martin f krafft wrote:- > There were [SC] when I created it, but I've recently > changed to > a signing subkey and removed the flag

Re: Key corruption: duplicate signatures and usage flags

martin f krafft writes: > [ Unknown signature status ] > Hey Justus, thanks for writing in. Here are the answers you wanted: > >> gpg --version please? > > 2.1.18 > >> > So far, so good. Do note the [SC] usage flags. >> >> What are the capabilities of your primary key

Re: Key corruption: duplicate signatures and usage flags

Justus Winter [2017-06-21 15:10:52+02] wrote: > martin f krafft writes: >> x-hkp://pool.sks-keyservers.net > > Here ^ is the keyserver url. >> gpg> save >> Preferred keyserver: Preferred keyserver: Preferred keyserver: Preferred >> keyserver: Preferred keyserver:

Re: Key corruption: duplicate signatures and usage flags

Hey Justus, thanks for writing in. Here are the answers you wanted: > gpg --version please? 2.1.18 > > So far, so good. Do note the [SC] usage flags. > > What are the capabilities of your primary key supposed to be? There were [SC] when I created it, but I've recently changed to a signing

Re: Key corruption: duplicate signatures and usage flags

Hi Martin, On Wed, 21 Jun 2017 at 11:03:40 +0200, martin f krafft wrote: > And then check this out: > > % gpg --edit-key 0x55C9882D999BBCC4 > […] > > key 55C9882D999BBCC4: > 24 duplicate signatures removed > > That's a bit weird. Where do these come from? The OpenPGP packets were not ordered

Re: Key corruption: duplicate signatures and usage flags

martin f krafft writes: > And then check this out: > > % gpg --edit-key 0x55C9882D999BBCC4 > gpg (GnuPG) 2.1.18; Copyright (C) 2017 Free Software Foundation, Inc. > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the

Re: Key corruption: duplicate signatures and usage flags

martin f krafft writes: > Hey, > > My key on the keyservers is 0x55C9882D999BBCC4. If I download this > to a fresh keyring, I get some weird behaviours: gpg --version please? > % alias gpg='gpg --homedir=.' I tend to do: $ export GNUPGHOME=$(mktemp -d) > So far, so

Re: Key corruption: duplicate signatures and usage flags

martin f. krafft [2017-06-21 11:03:40+02] wrote: > 24 duplicate signatures removed > > That's a bit weird. Where do these come from? I've seen the message with other keys too, just after --edit-key. The number of duplicate signatures varies. Next --refresh-keys command downloads the signatures