Imported secret subkey unusable "ssb#"
kloecker at kde.org
Sun Apr 18 21:55:59 CEST 2021
On Sonntag, 18. April 2021 02:06:40 CEST anon85786376 via Gnupg-users wrote:
> When a batch mode key is created with "Subkey-Type: ECC" and "Subkey-Curve:
> Ed25519", the key is generated without errors and appears to function
> normally. However, importing the secret keys will yield an unusable secret
> $ gpg -K
> sec rsa3072 2021-04-17 [SC]
> uid [ unknown] testkey
> ssb# ed25519 2021-04-17 [E]
I could reproduce the problem.
Note that the "#" next to the subkey indicates that the subkey is just a stub
for a secret key.
I noticed that after importing there are (as expected) two new files in
The names of those files should correspond to the keygrips of the primary key
and the subkey. This is true for the primary key, but the keygrip of the
subkey does not match.
$ gpg -K --with-keygrip FB489AAC37C42F19
sec rsa3072/FB489AAC37C42F19 2021-04-18 [SC]
Keygrip = 82380E8EB005D76AE6A1E73FCDC82B374B8D9584
uid [ unknown] testkey
ssb# ed25519/2C45A3D965A1FEFE 2021-04-18 [E]
Keygrip = B1838BACC3F53C98C675146D7E929AB285C6E49C
This seems to be the problem. gpg looks for a file named
B1838BACC3F53C98C675146D7E929AB285C6E49C.key which doesn't exist.
Please submit a bug report at https://dev.gnupg.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 195 bytes
Desc: This is a digitally signed message part.
More information about the Gnupg-users