saturneric / GpgFrontend

A free, open-source, robust yet user-friendly, compact and cross-platform tool for OpenPGP encryption. It stands out as an exceptional GUI frontend for the modern GnuPG (gpg).
https://gpgfrontend.bktus.com
GNU General Public License v3.0
522 stars 51 forks source link

GpgFrontend 2.1.4 for Linux doesn't give any option to create BrainPool keys. #175

Closed shamsuddin82 closed 3 months ago

shamsuddin82 commented 3 months ago

The windows version clearly give option to create ECDSA BrainPool for Key generation and ECDH BrainPool for Subkey generation. But the linux version doesn't give such option. Although this option was available in 2.1.3, but not any more.

saturneric commented 3 months ago

Please check the version of gnupg installed on your Linux system. If it is less than 2.3.0, some key algorithms will not appear.

shamsuddin82 commented 3 months ago

Please check the version of gnupg installed on your Linux system. If it is less than 2.3.0, some key algorithms will not appear.

It is lesser than 2.3 but if this is the case then why this option was available in gpgfrontend 2.1.3?

saturneric commented 3 months ago

I tested these algorithms in the later stages of the 2.1.4 development. On my machine, the gnupg version was 2.2.40. When I tested the Brainpool algorithm, I found a bug in gpg at this time: it could not infer whether to use ECDSA or ECDH from the type and purpose of the key, which prevented users from using GpgFrontend to generate Brainpool algorithm keys (including subkeys).

However, after testing, the same parameters worked properly in 2.4.x. I spent a long time searching, and I did found a ticket, but the development team member said that this worked in 2.4.x, without providing commit information about the fix. Therefore, I couldn't locate which version of gnupg fixed this bug. In the end, I could only increase the version requirement for the extended algorithms in GpgFrontend, and I set this value to 2.3.0, which is the gnupg version generating ECC algorithm keys by default.

By the way, after 2.3.0, gnupg provides support for more algorithms, such as X448, Ed448. It appears that it was ready to meet the challenges brought by various ECC key algorithms. So I can only speculate that this problem will not occur in most machines under this version.

shamsuddin82 commented 3 months ago

Thanks for your support!