Hints Switch off replacing the subject with three dots Previously in 19, Mozilla rejected to include (already implemented) OpenPGP/MIME functionality because they were preferring S/MIME according to Werner Koch. One Mozilla developer wrote about licensing concerns, but other people have pointed out that GPGME is GNU LGPL and the GNU GPL of GnuPG itself allows for a combined distribution of Thunderbird and GnuPG. It is unknown in public what the main reasons for doing a new implementation instead of using GnuPG (and Gpg4win) were. Enigmail's support for this version stopped. See the explanation of Enigmail's maintainer. A necessary and large change in how browser extensions can be implemented made Enigmail's technical implementation unfit for newer versions. The external extension Enigmail provided it, which used GnuPG. Until version 68 (last release 2020-10), Thunderbird did not have OpenPGP/MIME functionality included. The Thunderbird people have an FAQ about the new OpenPGP support. Thunderbird can still be configured to use a system's GnuPG installation for private key operations see. handling of hardware tokens like smardcards or usb devices. Some abilities that GnuPG provides are missing, e.g. The main drawback is that Thunderbird has its own handling of key material which is separated from the rest of the operating system and other applications that are using GnuPG for example. The main advantage for Thunderbird users is that they do not have to install an additional application like Gpg4win on Windows. Thunderbird (since version 78 first released 2020-07) implements its own OpenPGP/ MIME support, using the libraries RNP ( ) and Botan.
0 Comments
Leave a Reply. |