Thundrebird 45.2.0-2, GPG 2.1.14, On Manjaro Linux (Arch)
When importing public key attached to an email I'm greeted with "unable to import public key" error (from clicking IMPORT button, from importing file in key manager, or importing from clipboard). I can read the message but the key will not save permanently. Every other GPG activity seemed to work fine, certainly in relation to my own key pair and passphrase.
After exhausting every possible option I tried claws-mail which imported the key without issue. I ran into issues with sending from that claws though so nipped back into Thunderbird. The key is now correctly imported into GPG, and the email is decrypted as expected.
Happy to remove keys and debug if/as required. Looks just an integration issue with Enigmail and GPG2?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This may happen if the following three conditions are met:
(a) You have both GnuPG 1.4 and 2.x installed
(b) Claws is using GnuPG 1.4
(c) You're importing a very old-format certificate
GnuPG 1.4 had support for very old (25+ years) PGP certificate formats.
Recently, GnuPG has dropped support for these obsolete formats. Since
Enigmail requires a recent GnuPG, it would not be able to import such a
certificate. If your Claws installation is using GnuPG 1.4, it would be
able to.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thundrebird 45.2.0-2, GPG 2.1.14, On Manjaro Linux (Arch)
When importing public key attached to an email I'm greeted with "unable to import public key" error (from clicking IMPORT button, from importing file in key manager, or importing from clipboard). I can read the message but the key will not save permanently. Every other GPG activity seemed to work fine, certainly in relation to my own key pair and passphrase.
After exhausting every possible option I tried claws-mail which imported the key without issue. I ran into issues with sending from that claws though so nipped back into Thunderbird. The key is now correctly imported into GPG, and the email is decrypted as expected.
Happy to remove keys and debug if/as required. Looks just an integration issue with Enigmail and GPG2?
This may happen if the following three conditions are met:
(a) You have both GnuPG 1.4 and 2.x installed
(b) Claws is using GnuPG 1.4
(c) You're importing a very old-format certificate
GnuPG 1.4 had support for very old (25+ years) PGP certificate formats.
Recently, GnuPG has dropped support for these obsolete formats. Since
Enigmail requires a recent GnuPG, it would not be able to import such a
certificate. If your Claws installation is using GnuPG 1.4, it would be
able to.