also sprach Werner Koch <w...@gnupg.org> [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 % export GNUPGHOME=$(mktemp -d) % gpg --recv-key 55C9882D999BBCC4 % gpg --list-key 55C9882D999BBCC4 | grep '^pub' # [SC] % gpg --edit-key 55C9882D999BBCC4 save % gpg --list-key 55C9882D999BBCC4 | grep '^pub' # [C] Are you saying that gnupg 2.1.18 added the self-signature in the wrong place? Thanks, -- @martinkrafft | http://madduck.net/ | http://two.sentenc.es/ "i wish i hadn't slept all day, it's really lowered my productivity" -- robert mcqueen spamtraps: madduck.bo...@madduck.net
digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
