root@localhost:~# gpg --edit-key test01
gpg (GnuPG) 2.5.11; Copyright (C) 2025 g10 Code GmbH
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Secret key is available.
sec ed448/0x455FC46935C933AC
created: 2025-08-20 expires: never usage: SC
trust: ultimate validity: ultimate
ssb ky1024_cv448/0x0F02673C0FAF4984
created: 2025-08-20 expires: never usage: E
ssb ky768_bp256/0x126777B0E12B8042
created: 2025-08-20 expires: never usage: E
ssb ed25519/0xDEA53EEC37122D9C
created: 2025-08-20 expires: never usage: S
ssb ed25519/0x52342E9D08B4C030
created: 2025-08-20 expires: never usage: A
[ultimate] (1). test01
gpg> addkey
Please select what kind of key you want:
(3) DSA (sign only)
(4) RSA (sign only)
(5) Elgamal (encrypt only)
(6) RSA (encrypt only)
(7) DSA (set your own capabilities)
(8) RSA (set your own capabilities)
(10) ECC (sign only)
(11) ECC (set your own capabilities)
(12) ECC (encrypt only)
(13) Existing key
(14) Existing key from card
(16) ECC and Kyber
(17) Kyber (encrypt only)
Your selection? 16
Invalid selection.
Your selection?Description
Description
Details
Details
- Version
- gpg (GnuPG) 2.5.11
Revisions and Commits
Revisions and Commits
| rG GnuPG | |||
| rG48edcfdebc80 gpg: Fix list of possible algos for --edit-key. | |||
Related Objects
Related Objects
- Mentioned In
- T7756: Release GnuPG 2.5.12
Event Timeline
Comment Actions
I see from your other report that you are running a proper libgcrypt. But I think I spotted the bug: ECC+Kyber should not be displayed when adding a key. It is used for creating a new key ECC as primary and Kyber as subkey.