The GnuPG developers told me that most likely the crypto-library used by GnuPG is too old for using ellipitc curve algorithms. You can check the used version on the command line by typing:
gpg --version
I recommend that you create an RSA key (in key generation, in the Advanced tab).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh, it turns out I had both the old version (required for the operation of Linux Mint) and the new version (package gpg2) all time long.
I read on the Linux Mint forum that Enigmail is supposed to find the new version automatically, and in the Enigmail settings it says "GnuPG was found in /usr/bin/gpg2" (I checked, it is there).
But at least when it comes to key generation, Enigmail seems to use gpg instead of gpg2?
What to do about that?
The problem is not GnuPG itself, but libgcrypt (which does the crypto-work in GnuPG). You have libgcrypt version 1.6.5, but ECC keys are only supported as of version 1.8. The question is: why do you have such an old version of libgcrypt with a (relatively) new version of GnuPG?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not know. Updates come automatically, and according to the Synaptic Package Manager I have the latest version. The most recent update is from January:
libgcrypt20(1.6.5-2ubuntu0.6)xenial-security;urgency=medium*SECURITYUPDATE:ECDSAtimingattack-debian/patches/CVE-2019-13627.patch:addmitigationagainsttimingattackincipher/ecc-ecdsa.c,mpi/ec.c.-CVE-2019-13627-- Marc Deslauriers <marc.deslauriers@ubuntu.com> Mon, 13 Jan 2020 13:39:58 -0500
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well yes. It's just an old version that doesn't support ECC keys, no matter which version of GnuPG you have ... There is not much that we can do about it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I have trouble generating a new pair of keys with Enigmail 2.16 in
Thunderbird 68.8.0 64 bit on Linux Mint 18.3 64 bit.
I get this error message about 1 second after I click to confirm that I,
indeed, want to generate a new key pair:
"The key generation failed. Please check the Enigmail console (Menu
Enigmail > Debugging Options) for details."
The console, however, only contains the following, and I don't see any
error message or other helpful "details" there:
/usr/bin/gpg2 --charset utf-8 --display-charset utf-8
--no-auto-check-trustdb --batch --no-tty --no-verbose --status-fd 2
--gen-key%echo Generating key
Key-Type: EDDSA
Key-Curve: Ed25519
Key-Usage: sign
Subkey-Type: ECDH
Subkey-Curve: Curve25519
Subkey-Usage: encrypt
Name-Real: [name]
Name-Email: [email]
Expire-Date: 0
How may I find out why the key generation fails?
I have tried going with the default expiry of 5 years, but that doesn't
help. The only thing that changes is the last line in the console:
Expire-Date: 1825
TNX
Daniel
I'd recommend the Debugging Log, not the Console .
Menu Enigmail > Debugging Options -> View Log.
Aha! Thank you.
How do I find out which flag is invalid and how do I fix it?
This is the 1st time I see such an error. I'll ask for advice with GnuPG developers.
The GnuPG developers told me that most likely the crypto-library used by GnuPG is too old for using ellipitc curve algorithms. You can check the used version on the command line by typing:
I recommend that you create an RSA key (in key generation, in the
Advancedtab).Thank you very much. RSA seems to work.
I'll also check why we don't automatically get a newer GnuPG on Linux Mint.
Oh, it turns out I had both the old version (required for the operation of Linux Mint) and the new version (package gpg2) all time long.
I read on the Linux Mint forum that Enigmail is supposed to find the new version automatically, and in the Enigmail settings it says "GnuPG was found in /usr/bin/gpg2" (I checked, it is there).
But at least when it comes to key generation, Enigmail seems to use gpg instead of gpg2?
What to do about that?
Thank you.
Last edit: Daniel Sokolov 2020-06-18
Enigmail is using gpg2 (GnuPG version 2.1.11).
The problem is not GnuPG itself, but libgcrypt (which does the crypto-work in GnuPG). You have libgcrypt version 1.6.5, but ECC keys are only supported as of version 1.8. The question is: why do you have such an old version of libgcrypt with a (relatively) new version of GnuPG?
I do not know. Updates come automatically, and according to the Synaptic Package Manager I have the latest version. The most recent update is from January:
Well yes. It's just an old version that doesn't support ECC keys, no matter which version of GnuPG you have ... There is not much that we can do about it.