我刚刚在我的服务器上配置了 WKD,并且
gpg -v --auto-key-locate clear,wkd,nodefault --locate-key user@domain.com
我的大多数 uid/key 组合都按预期工作,除了一个地址 (olduser@domain.com) 链接到当前和撤销的密钥。上述命令的输出如下所示:
gpg: Note: RFC4880bis features are enabled.
gpg: using pgp trust model
gpg: pub rsa4096/68FD03F8C6AB1DE4 2016-06-15 Old User <olduser@domain.com>
gpg: Note: signature key 68FD03F8C6AB1DE4 expired Mon Jun 14 18:12:44 2021 CEST
gpg: key 68FD03F8C6AB1DE4: "Old Nickname <nickname@domain.com>" not changed
gpg: pub ed25519/7CD4656792B3A1F9 2022-06-06 Old User <newname@domain.com>
gpg: key 7CD4656792B3A1F9: "Old User <olduser@domain.com>" not changed
gpg: Total number processed: 2
gpg: unchanged: 2
gpg: auto-key-locate found fingerprint xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
gpg: Note: signature key 68FD03F8C6AB1DE4 expired Mon Jun 14 18:12:44 2021 CEST
gpg: automatically retrieved 'olduser@domain.com' via WKD
pub rsa4096 2016-06-15 [SC] [revoked: 2022-06-07]
51585E1318770F501D3CBDE968FD03F8C6AB1DE4
uid [ revoked] Old Nickname <nickname@domain.com>
uid [ revoked] Old User <olduser@domain.com>
uid [ revoked] Old Nickname2 <nickname2@domain.com>
sub rsa4096 2016-06-15 [E] [revoked: 2022-06-07]
即使 olduser@domain.com 是新密钥的主要 uid,gpg 也会显示此密钥的另一个 uid (newname@domain.com)。这很奇怪,但无关紧要。但随后 gpg 继续选择可通过 WKD 以某种方式获得的已撤销密钥。
https://metacode.biz/openpgp/web-key-directory上的 WKD 测试提供了类似的结果,但它显示了当前密钥和撤销密钥的指纹。
两个问题:
- 哪个 WKD 服务器托管我已撤销的密钥,使其优先于我在 domain.com 上的 WKD 服务器?
- 为什么 gpg 会选择过期和撤销的密钥而不是有效密钥?
谢谢,扬