Description of problem: Creating an key pair with the curve 448 looks like working. But the import/export fails. Version-Release number of selected component (if applicable): gnupg2-2.3.4-2.fc35.x86_64 How reproducible: every time Steps to Reproduce: 1. create an curve 448 key pair on system a 2. export the key on system a 3. try to import it on system b Actual results: Only the public key is imported an the private one are ignored with the error about an invalid key. Expected results: That both key's are imported. Additional info: Both systems are running on fedora 35 with all updates. Import message: gpg: key E0A2F105A79BACD5: public key "FOO" imported gpg: key E0A2F105A79BACD5/E0A2F105A79BACD5: error sending to agent: Bad secret key gpg: key E0A2F105A79BACD5/FBDC19AB07E17007: error sending to agent: Bad secret key gpg: error reading '/tmp/bla.text': Bad secret key gpg: import from '/tmp/bla.text' failed: Bad secret key gpg: Total number processed: 0 gpg: imported: 1 gpg: secret keys read: 1
Just tested with Fedora 37, which has gnupg2-2.3.8-1.fc37.x86_64 and it looks like I am getting the same error. Let me investigate the issue further
I was not able to get much further so I opened an upstream bug with the information I was able to collect so far: https://dev.gnupg.org/T6294
The upstream issue is resolved. Do you need to backport the fix to some specific Fedora version or is it ok to wait for the next upstream release?
Thanks, no for me it will be ok ti wait for the next upstream release. I found the problem only at the testing stage for the 448 as an replacement for 25519.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
This should be fixed in rawhide and Fedora 38 now as it has the 2.4.0 version.