Thunderbird Beta and Release: External GnuPG Keys Not Working with GnuPG 2.5.x
DEUTSCH (English see below(:
Hallo zudammen,
Konfiguration: - Window11 25H2 (aktuell) - Thunderbird Beta-6 (BuildID=20260213180051) - gpg2.5.17 (Gpg4Win 5.0.1); siehe auch: <https://www.gpg4win.de/>
Der bisherige und standarmärige Installationspfad von "Gpg4Win": "C:\Progam Diles (x86)\Gpg4Win\" wurde softwareseitig auf: "C:\Progam Diles\Gpg4Win\" geändert!
Bug 1967121 (Closed) => thunderbird148 --- fixed! <https://bugzilla.mozilla.org/show_bug.cgi?id=1967121>
Zur Zeit verfolge ich die Änderungen bezüglich der externen Schlüsselverwaltung in Thunderbird-Beta, da das Arbeiten mit externen Schlüsseln in der esr- und in der relesease-Version von Thunderbird seit der offiziellen Herausgabe von gpg2.5.x absolut nicht mehr möglich ist! Die geheimen Schlüssel für das Entschlüsseln und Signieren werden mit gpg2.5.x nicht mehr gefunden!
In der Schlüsselverwaltung von TB-Beta befinden sich meine öffentlichen Schlüssel und alle öffentlichen Schlüssel meiner Kommunikationspartner. Extern sind meine geheimen Schlüssel gelagert. Folgende Präferenz wurde aufgrund von gpg2.5.x hinzugefügt:
Allerdings erscheint nach all diesen Maßnahmen die Fehlermeldung: "The secret key that's required to decrypt this message is not availlable."
Mit Herausgabe von Thunderbird/148.0 (release) sind dort die gleichen Probleme mit der externen Schlüsselverwaltung zu bepbachten!
Mit Versionen gpg < 2.5 funktioniert unter Windows alles problemlos!
UNTER LINUX haben hier Änderungen an der Präferenz: "mail.openpgp.load_untested_gpgme_version" nachweislich keinerlei Auswirkungen!
Was übersehe ich?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ENGLISH:
Hello,
Configuration: - Window11 25H2 (current status) - Thunderbird Beta-6 (BuildID=20260213180051) - gpg2.5.17 (Gpg4Win 5.0.1); see also: <https://www.gpg4win.de/>
The previous and default installation path of "Gpg4Win": "C:\Program Files (x86)\Gpg4Win\" has been changed by the software to: "C:\Program Files\Gpg4Win\"!
Bug 1967121 (Closed) => thunderbird148 --- fixed! <https://bugzilla.mozilla.org/show_bug.cgi?id=1967121>
At the moment, I’m following the changes regarding external key management in Thunderbird Beta, because working with external keys in the ESR and release versions of Thunderbird has become absolutely impossible since the official release of gpg 2.5.x! The secret keys required for decryption and signing are no longer found when using gpg 2.5.x!
In Thunderbird Beta’s key manager, my public keys and all public keys of my communication partners are present. My secret keys are stored externally. The following preference was added because of gpg 2.5.x:
However, even after all these measures, the following error message appears: **"The secret key that's required to decrypt this message is not available."**
With the release of Thunderbird 148.0 (release), the same problems with external key management can be observed there as well!
With gpg versions **older than 2.5**, everything works flawlessly under Windows!
- UNDER LINUX**, changes to the preference
"mail.openpgp.load_untested_gpgme_version" have demonstrably no effect at all!
What am I missing?
Krejt Përgjigjet (6)
You're not alone, I'm having the exact same problem with TB148.0 and gpg4win 5.0.1 on Windows. I'd suggest you post the problem to the Thunderbird e2ee mailing list at Topicbox. https://thunderbird.topicbox.com/groups/e2ee
Ndryshuar nga christ1
I appreciate the suggestion to post this issue on the Thunderbird e2ee mailing list, but I prefer not to create another account, install additional authentication apps, or provide personal data to yet another external service.
Because this problem affects multiple users, occurs on both Windows and Linux, and persists even though it is reportedly fixed in the current Beta, I kindly ask the moderators to forward this thread to the e2ee team or the appropriate developers.
The issue is reproducible, involves external OpenPGP key handling with GnuPG 2.5.x, and appears to affect Thunderbird ESR, Release, and Beta versions alike. It would be very helpful if the responsible team could take a closer look.
Thanks ThoBa
I'm running Debian GNU/Linux (testing), with GPG 2.4.x, Thunderbird Beta (149.0b1). Setting the `mail.openpgp.load_untested_gpgme_version` setting to `45` worked for me a few weeks ago, though it seems like that is no longer necessary on beta builds at least (that is, external smartcard operations still work with the setting empty). Peeking at the code, beta builds appear to add the 45 version as a permutation to try out-of-the-box. And, sure enough, it does get loaded:
``` $ lsof -p 2161757 | grep -i gpgme thunderbi 2161757 preston mem REG 254,1 359752 178428159 /usr/lib/x86_64-linux-gnu/libgpgme.so.45.0.1 ```
I'm running Debian GNU/Linux (testing), with GPG 2.4.x
The problem is with gpg 2.5.x.
Duhet të bëni hyrjen te llogaria juaj që t’i përgjigjeni postimeve. Ju lutemi, filloni me një pyetje të re, nëse s’keni ende një llogari.