如何在不导入的情况下显示gpg密钥详细信息?

时间:2014-03-03 01:10:44

标签: gnupg openpgp

我有postgresql apt存储库gpg密钥的副本,并希望查看文件中的gpg密钥的详细信息。如果不将它导入密钥环,这可能吗?

8 个答案:

答案 0 :(得分:120)

在查看OpenPGP密钥数据时,您可以获得几个详细级别:基本摘要,此摘要的机器可读输出或各个OpenPGP数据包的详细(非常技术性)列表。

基本密钥信息

对于OpenPGP密钥文件的简短峰值,您只需通过STDIN将文件名作为参数或管道传递给密钥数据。如果没有传递命令,GnuPG会尝试猜测你想要做什么 - 对于关键数据,这是在密钥上打印摘要:

$ gpg a4ff2279.asc
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa8192 2012-12-25 [SC]
      0D69E11F12BDBA077B3726AB4E1F799AA4FF2279
uid           Jens Erat (born 1988-01-19 in Stuttgart, Germany)
uid           Jens Erat <jens.erat@fsfe.org>
uid           Jens Erat <jens.erat@uni-konstanz.de>
uid           Jens Erat <jabber@jenserat.de>
uid           Jens Erat <email@jenserat.de>
uid           [jpeg image of size 12899]
sub   rsa4096 2012-12-26 [E] [revoked: 2014-03-26]
sub   rsa4096 2012-12-26 [S] [revoked: 2014-03-26]
sub   rsa2048 2013-01-23 [S] [expires: 2023-01-21]
sub   rsa2048 2013-01-23 [E] [expires: 2023-01-21]
sub   rsa4096 2014-03-26 [S] [expires: 2020-09-03]
sub   rsa4096 2014-03-26 [E] [expires: 2020-09-03]
sub   rsa4096 2014-11-22 [A] [revoked: 2016-03-01]
sub   rsa4096 2016-02-24 [A] [expires: 2020-02-23]

设置--keyid-format 0xlong, long key IDs are printed而不是insecure short key IDs

$ gpg a4ff2279.asc                                                                 
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa8192/0x4E1F799AA4FF2279 2012-12-25 [SC]
      0D69E11F12BDBA077B3726AB4E1F799AA4FF2279
uid                             Jens Erat (born 1988-01-19 in Stuttgart, Germany)
uid                             Jens Erat <jens.erat@fsfe.org>
uid                             Jens Erat <jens.erat@uni-konstanz.de>
uid                             Jens Erat <jabber@jenserat.de>
uid                             Jens Erat <email@jenserat.de>
uid                             [jpeg image of size 12899]
sub   rsa4096/0x0F3ED8E6759A536E 2012-12-26 [E] [revoked: 2014-03-26]
sub   rsa4096/0x2D6761A7CC85941A 2012-12-26 [S] [revoked: 2014-03-26]
sub   rsa2048/0x9FF7E53ACB4BD3EE 2013-01-23 [S] [expires: 2023-01-21]
sub   rsa2048/0x5C88F5D83E2554DF 2013-01-23 [E] [expires: 2023-01-21]
sub   rsa4096/0x8E78E44DFB1B55E9 2014-03-26 [S] [expires: 2020-09-03]
sub   rsa4096/0xCC73B287A4388025 2014-03-26 [E] [expires: 2020-09-03]
sub   rsa4096/0x382D23D4C9773A5C 2014-11-22 [A] [revoked: 2016-03-01]
sub   rsa4096/0xFF37A70EDCBB4926 2016-02-24 [A] [expires: 2020-02-23]
pub   rsa1024/0x7F60B22EA4FF2279 2014-06-16 [SCEA] [revoked: 2016-08-16]

提供-v-vv甚至可以添加更多信息。在这种情况下,我更喜欢打印包装细节(见下文)。

机读输出

GnuPG还有一个冒号分隔的输出格式,可以轻松解析并具有稳定的格式。 format is documented in GnuPG doc/DETAILS file。{{3}}。接收此格式的选项为--with-colons

$ gpg --with-colons a4ff2279.asc
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub:-:8192:1:4E1F799AA4FF2279:1356475387:::-:
uid:::::::::Jens Erat (born 1988-01-19 in Stuttgart, Germany):
uid:::::::::Jens Erat <jens.erat@fsfe.org>:
uid:::::::::Jens Erat <jens.erat@uni-konstanz.de>:
uid:::::::::Jens Erat <jabber@jenserat.de>:
uid:::::::::Jens Erat <email@jenserat.de>:
uat:::::::::1 12921:
sub:-:4096:1:0F3ED8E6759A536E:1356517233:1482747633:::
sub:-:4096:1:2D6761A7CC85941A:1356517456:1482747856:::
sub:-:2048:1:9FF7E53ACB4BD3EE:1358985314:1674345314:::
sub:-:2048:1:5C88F5D83E2554DF:1358985467:1674345467:::
sub:-:4096:1:8E78E44DFB1B55E9:1395870592:1599164118:::
sub:-:4096:1:CC73B287A4388025:1395870720:1599164118:::
sub:-:4096:1:382D23D4C9773A5C:1416680427:1479752427:::
sub:-:4096:1:FF37A70EDCBB4926:1456322829:1582466829:::

从GnuPG 2.1.23开始,使用gpg: WARNING: no command supplied. Trying to guess what you mean ...选项和--import-options show-only命令可以省略--import警告(当然,这也可以在没有--with-colons的情况下使用} ):

$ gpg --with-colons --import-options show-only --import a4ff2279
[snip]

对于旧版本:STDERR上会显示警告消息,因此您只需读取STDIN即可将警告中的关键信息拆分。

技术细节:列出OpenPGP数据包

如果不安装任何其他软件包,您可以使用 gpg --list-packets [file] 查看文件中包含的OpenPGP数据包的信息。

$ gpg --list-packets a4ff2279.asc
:public key packet:
    version 4, algo 1, created 1356475387, expires 0
    pkey[0]: [8192 bits]
    pkey[1]: [17 bits]
    keyid: 4E1F799AA4FF2279
:user ID packet: "Jens Erat (born 1988-01-19 in Stuttgart, Germany)"
:signature packet: algo 1, keyid 4E1F799AA4FF2279
    version 4, created 1356516623, md5len 0, sigclass 0x13
    digest algo 2, begin of digest 18 46
    hashed subpkt 27 len 1 (key flags: 03)
[snip]

pgpdump [file] 工具的工作方式与gpg --list-packets类似,并提供类似的输出,但会将所有这些算法标识符解析为可读表示形式。它可用于所有相关的发行版(在Debian衍生版本中,该包被称为pgpdump,就像工具本身一样。)

$ pgpdump a4ff2279.asc
Old: Public Key Packet(tag 6)(1037 bytes)
    Ver 4 - new
    Public key creation time - Tue Dec 25 23:43:07 CET 2012
    Pub alg - RSA Encrypt or Sign(pub 1)
    RSA n(8192 bits) - ...
    RSA e(17 bits) - ...
Old: User ID Packet(tag 13)(49 bytes)
    User ID - Jens Erat (born 1988-01-19 in Stuttgart, Germany)
Old: Signature Packet(tag 2)(1083 bytes)
    Ver 4 - new
    Sig type - Positive certification of a User ID and Public Key packet(0x13).
    Pub alg - RSA Encrypt or Sign(pub 1)
    Hash alg - SHA1(hash 2)
    Hashed Sub: key flags(sub 27)(1 bytes)
[snip]

答案 1 :(得分:27)

我似乎能够简单地相处:

$gpg <path_to_file>

这样的输出:

$ gpg /tmp/keys/something.asc 
  pub  1024D/560C6C26 2014-11-26 Something <something@none.org>
  sub  2048g/0C1ACCA6 2014-11-26

操作系统没有具体说明哪些关键信息是相关的。这个输出是我关心的。

答案 2 :(得分:24)

要验证并列出密钥的指纹(不先将其导入密钥环),请键入

gpg --with-fingerprint <filename>

答案 3 :(得分:5)

选项--list-packets解析文件中的pgp数据并以非常技术的方式输出其结构。解析公钥时,您可以轻松提取用户ID和签名的密钥ID。

请注意,此命令解析数据格式,不会对签名或类似内容进行验证。

答案 4 :(得分:2)

当我偶然发现这个答案时,我正在寻找一种方法来获得易于解析的输出。对我来说,选项--with-colons可以解决问题:

$ gpg --with-colons file
sec::4096:1:AAAAAAAAAAAAAAAA:YYYY-MM-DD::::Name (comment) email
ssb::4096:1:BBBBBBBBBBBBBBBB:YYYY-MM-DD::::

可以找到文档here

答案 5 :(得分:1)

您也可以使用--keyid-format开关显示短键ID或长键ID:

$ gpg2 -n --with-fingerprint --keyid-format=short --show-keys <filename>

输出如下(来自PostgreSQL CentOS仓库密钥的示例):

pub   dsa1024/442DF0F8 2008-01-08 [SCA]                                                                       │
      Key fingerprint = 68C9 E2B9 1A37 D136 FE74  D176 1F16 D2E1 442D F0F8                                    │              honor-keyserver-url
uid                    PostgreSQL RPM Building Project <pgsqlrpms-hackers@pgfoundry.org>                      │                     When  using --refresh-keys, if the key in question has a preferred keyserver URL, then use that
sub   elg2048/D43F1AF8 2008-01-08 [E]

答案 6 :(得分:1)

要获取密钥ID(8个字节,16个十六进制数字),这是在GPG 1.4.16、2.1.18和2.2.19中对我有用的命令:

gpg --list-packets <key.asc | awk '$1=="keyid:"{print$2}'

要获取更多信息(除了密钥ID):

gpg --list-packets <key.asc

要获取更多信息:

gpg --list-packets -vvv --debug 0x2 <key.asc

命令

gpg --dry-run --import <key.asc

在所有3个版本中也都适用,但是在GPG 1.4.16中,它仅打印短(4字节,8个十六进制数字)密钥ID,因此识别密钥的安全性较低。

其他答案中的某些命令(例如gpg --show-keysgpg --with-fingerprintgpg --import --import-options show-only)在上述3个GPG版本中的某些版本中不起作用,因此在定位多个版本时它们不可移植GPG。

答案 7 :(得分:0)

pgpdumphttps://www.lirnberger.com/tools/pgpdump/)是可用于检查pgp块的工具。

它不是用户友好的,但是相当技术性,

  • 它解析公钥或私钥(无警告)
  • 它不会修改任何密钥环(根据我的经验,有时不清楚gpg在幕后做了什么)
  • 它打印所有数据包,特别是显示有关密钥的各种文本数据的userid数据包。
pgpdump -p test.asc 
New: Secret Key Packet(tag 5)(920 bytes)
    Ver 4 - new
    Public key creation time - Fri May 24 00:33:48 CEST 2019
    Pub alg - RSA Encrypt or Sign(pub 1)
    RSA n(2048 bits) - ...
    RSA e(17 bits) - ...
    RSA d(2048 bits) - ...
    RSA p(1024 bits) - ...
    RSA q(1024 bits) - ...
    RSA u(1020 bits) - ...
    Checksum - 49 2f 
New: User ID Packet(tag 13)(18 bytes)
    User ID - test (test) <tset>                        
New: Signature Packet(tag 2)(287 bytes)
    Ver 4 - new
    Sig type - Positive certification of a User ID and Public Key packet(0x13).
    Pub alg - RSA Encrypt or Sign(pub 1)
    Hash alg - SHA256(hash 8)
    Hashed Sub: signature creation time(sub 2)(4 bytes)
        Time - Fri May 24 00:33:49 CEST 2019
    Hashed Sub: issuer key ID(sub 16)(8 bytes)
        Key ID - 0x396D5E4A2E92865F
    Hashed Sub: key flags(sub 27)(1 bytes)
        Flag - This key may be used to certify other keys
        Flag - This key may be used to sign data
    Hash left 2 bytes - 74 7a 
    RSA m^d mod n(2048 bits) - ...
        -> PKCS-1

不幸的是,它没有读stdin:/