Thanks for pointing out that the signature key and the authentication
keys are identical:
$ gpg --card-status
[…]
Signature key ....: 7A0F E73D DB74 4F0F 9734 1DA7 1BE3 49D1 1B6E
D589
created ....: 2023-06-29 03:50:43
Encryption key....: DBBD 3239 D0F1 4326 808D FC8F 7CC0 2D68 D2E3
1736
created ....: 2023-06-29 03:50:43
Authentication key: 7A0F E73D DB74 4F0F 9734 1DA7 1BE3 49D1 1B6E
D589
created ....: 2023-06-29 03:50:43
[…]
sec> rsa4096/1BE349D11B6ED589 created: 2023-06-29 expires: never
card-no: 0006 18698015
ssb> rsa4096/7CC02D68D2E31736 created: 2023-06-29 expires: never
card-no: 0006 18698015
ssb# rsa4096/32B106F6877CC64B created: 2023-11-22 expires: never
At the same time, the key IDs are different:
$ gpg --list-keys --keyid-format LONG yubi...@f76.eu
pub rsa4096/1BE349D11B6ED589 2023-06-29 [SC]
7A0FE73DDB744F0F97341DA71BE349D11B6ED589
uid [ultimate] Felix E. Klee (YubiKey) <yubi...@f76.eu>
sub rsa4096/7CC02D68D2E31736 2023-06-29 [E]
sub rsa4096/32B106F6877CC64B 2023-11-22 [A]
How does that go together?
I thought the long key ID is the last 16 characters of the fingerprint.
And the fingerprint is a 40 character hash of the public (or private?)
key.
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
