Key corruption: duplicate signatures and usage flags

[Teemu Likonen]

Justus Winter [2017-06-21 15:10:52+02] wrote:

> martin f krafft <madduck at madduck.net> writes:
>>     x-hkp://pool.sks-keyservers.net
>
> Here  ^ is the keyserver url.

>>   gpg> save
>>   Preferred keyserver: Preferred keyserver: Preferred keyserver: Preferred keyserver: Preferred keyserver: Preferred keyserver: Preferred keyserver: %
>
> And these are the labels for these urls.  This was a cosmetic problem
> that I just fixed.

There is similar cosmetic problem with --update-trustdb:

    [...]
    No trust value assigned to:
    pub   rsa4096 XXXX-XX-XX [SC]
          [...]
     Primary key fingerprint: [...]

    Please decide how far you trust this user to correctly verify other
    users' keys (by looking at passports, checking fingerprints from
    different sources, etc.)

      1 = I don't know or won't say
      2 = I do NOT trust
      3 = I trust marginally
      4 = I trust fully
      s = skip this key
      q = quit

    Your decision? 4
    gpg: depth: 4  valid:  17  signed:  13  trust: 0-, 0q, 0n, 3m, 14f, 0u
    gpg: next trustdb check due at 2017-09-09

And when the whole session is over gpg prints fingerprints of _all_ keys
that got their ownertrust updated.

-- 
/// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: </pipermail/attachments/20170622/75ec50dc/attachment.sig>