Mailing List Archive

GnuPG 2.3.1 released

We are pleased to announce the availability of a new GnuPG release:
version 2.3.1. This is the second release in the new 2.3 series which
fixes a couple of bugs and adds a few new things. See below for details.

Although some bugs might linger in the 2.3 versions, they are intended
to replace the 2.2 series. 2.3 may even be used for production purposes
if either the risk of minor regressions is acceptable or the new
features are important.

What is GnuPG

The GNU Privacy Guard (GnuPG, GPG) is a complete and free implementation
of the OpenPGP and S/MIME standards.

GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public key
directories. GnuPG itself is a command line tool with features for easy
integration with other applications. The separate library GPGME provides
a uniform API to use the GnuPG engine by software written in common
programming languages. A wealth of frontend applications and libraries
making use of GnuPG are available. As an universal crypto engine GnuPG
provides support for S/MIME and Secure Shell in addition to OpenPGP.

GnuPG is Free Software (meaning that it respects your freedom). It can
be freely used, modified and distributed under the terms of the GNU
General Public License.

Three different versions of GnuPG are actively maintained:

- This version (2.3) is the latest development with a lot of new
features. This announcement is about the first release of this

- Version 2.2 is our LTS (long term support) version and guaranteed to
be maintained at least until the end of 2024.

- Version 1.4 is maintained to allow decryption of very old data which
is, for security reasons, not anymore possible with other GnuPG

Noteworthy changes in version 2.3.1

* The new configuration file common.conf is now used to enable the
use of the key database daemon with "use-keyboxd". Using this
option in gpg.conf and gpgsm.conf is supported for a transitional
period. See doc/example/common.conf for more.

* gpg: Force version 5 key creation for ed448 and cv448 algorithms.

* gpg: By default do not use the self-sigs-only option when
importing from an LDAP keyserver. [#5387]

* gpg: Lookup a missing public key of the active card via LDAP.

* gpgsm: New command --show-certs. [51419d6341]

* scd: Fix CCID driver for SCM SPR332/SPR532. [#5297]

* scd: Further improvements for PKCS#15 cards.

* Fix build problems on Fedora. [#5389]

* Fix build problems on macOS. [#5400]

* New configure option --with-tss to allow the selection of the TSS
library. [93c88d0af3]


Getting the Software

Please follow the instructions found at <> or
read on:

GnuPG may be downloaded from one of the GnuPG mirror sites or direct
from its primary FTP server. The list of mirrors can be found at
<>. Note that GnuPG is not
available at

The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here: (7392k)

An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here: (4570k)

The source used to build the Windows installer can be found in the same
directory with a ".tar.xz" suffix.

A new version of Gpg4win featuring this version of GnuPG will be
released soon. In the meantime it is possible to install this GnuPG
version on top of Gpg4win 3.1.15.

Checking the Integrity

In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:

* If you already have a version of GnuPG installed, you can simply
verify the supplied signature. For example to verify the signature
of the file gnupg-2.3.1.tar.bz2 you would use this command:

gpg --verify gnupg-2.3.1.tar.bz2.sig gnupg-2.3.1.tar.bz2

This checks whether the signature file matches the source file.
You should see a message indicating that the signature is good and
made by one or more of the release signing keys. Make sure that
this is a valid key, either by matching the shown fingerprint
against a trustworthy list of valid release signing keys or by
checking that the key has been signed by trustworthy other keys.
See the end of this mail for information on the signing keys.

* If you are not able to use an existing version of GnuPG, you have
to verify the SHA-1 checksum. On Unix systems the command to do
this is either "sha1sum" or "shasum". Assuming you downloaded the
file gnupg-2.3.1.tar.bz2, you run the command like this:

sha1sum gnupg-2.3.1.tar.bz2

and check that the output matches the next line:

a8f66ba4f7dcb2e7322aef786f942ce5ccca6f14 gnupg-2.3.1.tar.bz2
8e81d5592b0f3c88c3b5c9928ec4bc50e811357b gnupg-w32-2.3.1_20210420.tar.xz
af13b1620c234dd6124531ad2698827caaaa6287 gnupg-w32-2.3.1_20210420.exe


This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian,
Japanese, Norwegian, Polish, Russian, and Ukrainian being almost
completely translated.

Documentation and Support

The file has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details available only in the manual. The manual is also available
online at

or can be downloaded as PDF at

You may also want to search the GnuPG mailing list archives or ask on
the gnupg-users mailing list for advise on how to solve problems. Most
of the new features are around for several years and thus enough public
experience is available. has user contributed
information around GnuPG and relate software.

In case of build problems specific to this release please first check for updated information.

Please consult the archive of the gnupg-users mailing list before
reporting a bug:
We suggest to send bug reports for a new release to this list in favor
of filing a bug at If you need commercial
support go to or

If you are a developer and you need a certain feature for your project,
please do not hesitate to bring it to the gnupg-devel mailing list for


Since 2001 maintenance and development of GnuPG is done by g10 Code GmbH
and still mostly financed by donations. Three full-time employed
developers as well as two contractors exclusively work on GnuPG and
closely related software like Libgcrypt, GPGME and Gpg4win.

We like to thank all the nice people who are helping the GnuPG project,
be it testing, coding, translating, suggesting, auditing, administering
the servers, spreading the word, or answering questions on the mailing

The financial support of the governmental CERT of Luxembourg
(GOVCERT.LU) allowed us to develop new and improved features for
smartcards (Yubikey, PIV and Scute) as well as various usability
features. Thanks.

Many thanks also to all other financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good and secure shape and to address all the small and larger requests
made by our users.

Happy hacking,

Your GnuPG hackers

This is an announcement only mailing list. Please send replies only to
the gnupg-users at mailing list.

List of Release Signing Keys:
To guarantee that a downloaded GnuPG version has not been tampered by
malicious entities we provide signature files for all tarballs and
binary versions. The keys are also signed by the long term keys of
their respective owners. Current releases are signed by one or more
of these four keys:

ed25519 2020-08-24 [expires: 2030-06-30]
Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA
Werner Koch (dist signing 2020)

rsa3072 2017-03-17 [expires: 2027-03-15]
Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28
Andre Heinecke (Release Signing Key)

rsa2048 2011-01-12 [expires: 2021-12-31]
Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
Werner Koch (dist sig)

The keys are available at and
in any recently released GnuPG tarball in the file g10/distsigkey.gpg .
Note that this mail has been signed by a different key.

"If privacy is outlawed, only outlaws will have privacy."
- PRZ 1991