Hello!

We are pleased to announce the availability of a new GnuPG release:
Version 2.5.22.  This version is mainly a bug fixing release.

The main features in the 2.5 series are improvements for 64 bit Windows
and the introduction of Kyber (aka ML-KEM or FIPS-203) as PQC encryption
algorithm.  Other than PQC support the 2.6 series will not differ a lot
from 2.4 because the majority of changes are internal to make use of
newer features from the supporting libraries.  Keep in mind that the 2.4
series has reached end-of-life.  Thus expect no more updates for 2.4.
As always with GnuPG, new versions are fully compatible with previous
versions.


What is GnuPG
=============

The GNU Privacy Guard (GnuPG, GPG) is a complete and free implementation
of the OpenPGP, S/MIME, and Gpg-Agent 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.


Noteworthy changes in version 2.5.22 (2026-08-31)
=================================================
         [compared to version 2.5.21]

 * New and extended features:

   - gpg: New option "primary" for the --card-edit "generate" command.
     This option is useful create only the primary key on the first
     slot of an OpenPGP card.  [T8344]

   - Make detection of the installation directory work for macOS.
     [rG0be940905d]

   - gpgsm: Emit issuer and serial no. when the certificate is not
     found.  [T8363]

 * Bug fixes:

   - gpg: Fix trustdb recursive lock problem.  [T8317]

   - gpg: Fix using wrong fingerprint length for the intended
     recipient fingerprint.  [T8330]

   - gpg: Fix wrong assertion edge case in building packets.
     [rGe319d82d7e]

   - gpg: Fix possible double free in import_revoke_cert.  [T8328]

   - gpg: Fix long standing regression of "bkuptocard".
     [T8344,rGf103eaee63]

   - gpg: Fix TOFU trust models to actually check UTK signatures.
     [T8404]

   - gpg: Don't enable the partial file guard if already done.  Fix
     regression introduced by partial file guards.  [T8399]

   - gpgsm: Only display de-vs compliance status in de-vs compliance
     mode.  [T8333]

   - gpgsm: Return 0 if decryption of multi recipient file succeeds.
     [T8340]

   - gpgsm: Check args for special file names and dashes.  [T8347]

   - gpgsm: Fix keydb_get_flags with keyboxd.  [T8048]

   - g13: Add sanity check on the syntax of the dmsetup algo string.
     [rG386c3e63b1]

 * Other changes:

   - gpg,gpgsm: Emit signing time as status output also for bad
     signatures.  [T8364]

   - gpg: Emit status line for failed write.  [T8398]

   - scd: Put a workaround for buggy CCID device.  [T8331]

   - scd: Allow switching APP when --pcsc-shared is enabled.
     [rGf783c02525]

   - gpgconf: Print a warning on Windows on insufficent global config
     directory permissions.  [rG56eb3148c7]

 Release-info: https://dev.gnupg.org/T8320


Getting the Software
====================

Please follow the instructions found at <https://gnupg.org/download/> or
read on:

GnuPG may be downloaded from one of the GnuPG mirror sites or direct
from its primary file server.  The list of mirrors can be found at
<https://gnupg.org/download/mirrors.html>.  Note that GnuPG is not
available at ftp.gnu.org.

The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:

 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.5.22.tar.bz2 (8167k)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.5.22.tar.bz2.sig

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

 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.5.22_20260831.exe (5641k)
 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.5.22_20260831.exe.sig

The source used to build this installer for 64-bit Windows is available as

 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-w32-2.5.22_20260831.tar.xz (15M)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-w32-2.5.22_20260831.tar.xz.sig

This source tarball may also be used to download all required libraries
at once to build a Unix version on any modern system.  See the included
README.


Debian Packages
===============

We also provide Debian style packages for a couple of Debian variants.
See https://repos.gnupg.org/deb/gnupg/trixie/ or use the menu to switch
to other distros/releases.  If you encounter packaging problems please
report them to the gnupg-devel mailing list.  It may however take a few
days until they are available.


Windows Installer
=================

A new version of Gpg4win will be released soon.  For those who are
affected by one of the now fixed bugs, it is possible to install the
simple Windows installer mentioned above on top of Gpg4win 5.1.0.


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.5.22.tar.bz2 you would use this command:

     gpg --verify gnupg-2.5.22.tar.bz2.sig gnupg-2.5.22.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.5.22.tar.bz2, you run the command like this:

     sha1sum gnupg-2.5.22.tar.bz2

   and check that the output matches the next line:

4921a199ae868c8dd0478352d2d93bb470489e23  gnupg-2.5.22.tar.bz2
60af5b0ce190005f9fd9b5562b1e939fd9006af4  gnupg-w32-2.5.22_20260831.tar.xz
66b3de1ba9179ced49ecbb0dfccb26d5b08ae4d0  gnupg-w32-2.5.22_20260831.exe


Internationalization
====================

This version of GnuPG has support for 26 languages with Chinese, Czech,
Dutch, French, Georgian, German, Italian, Japanese, Norwegian, Polish,
Portuguese, Russian, Turkish, and Ukrainian being almost completely
translated.


Documentation and Support
=========================

The file gnupg.info 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

  https://gnupg.org/documentation/manuals/gnupg/

or can be downloaded as PDF at

  https://gnupg.org/documentation/manuals/gnupg.pdf

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.  https://wiki.gnupg.org has user contributed
information around GnuPG and relate software.

If you are using cleartext signatures in your application please read
https://gnupg.org/blog/20251226-cleartext-signatures.html and maybe
https://gnupg.com/20260122-39C3_reply_gpg_fail.html

In case of build problems specific to this release please try to first
check https://dev.gnupg.org/T8320 for updated information.  We are sorry
that due to ongoing DoS on this service, you may end up at a "is under
maintenance page".  Static copies of the ticket pages are provided
unless the DoS is too heavy.

Please consult the archive of the gnupg-users mailing list before
reporting a bug: https://gnupg.org/documentation/mailing-lists.html.
We suggest to send bug reports for a new release to this list in favor
of filing a bug at https://bugs.gnupg.org.  If you need commercial
support go to https://gnupg.com or https://gnupg.org/service.html.

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
discussion.


Thanks
======

Since 2001 maintenance and development of GnuPG is done by g10 Code GmbH
and has mostly been financed by donations.  A team of full-time employed
developers and contractors are working exclusively on GnuPG and related
software like Libgcrypt, GPGME, Kleopatra, Okular, and Gpg4win.

Fortunately, and this is still not common with free software, we have
established a way of financing the development while keeping all our
software free and freely available for everyone.  Our model is similar
to the way RedHat manages RHEL and Fedora: Except for the actual binary
of the MSI installer for Windows and client specific configuration
files, all the software is available under the GNU GPL and other Open
Source licenses.  Thus customers may even build and distribute their own
version of the software as long as they do not use our trademarks
GnuPG Desktop® or GnuPG VS-Desktop®.

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, answering questions on the mailing
lists, or helped with donations.

*Thank you all*

   Your GnuPG hackers


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

* List of Release Signing Keys:
  To guarantee that a downloaded 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 five keys:

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

    ed25519 2021-05-19 [SC] [expires: 2027-04-04]
    AC8E 115B F73E 2D8D 47FA  9908 E98E 9B2D 19C6 C8BD
    Niibe Yutaka (GnuPG Release Key)

    rsa3072 2025-05-09 [SC] [expires: 2033-03-03]
    3B76 1AE4 E63B F351 9CE7  D63B ECB6 64CB E133 2EEF
    Alexander Kulbartsch (GnuPG Release Key)

    ed25519 2026-07-20 [SC] [expires: 2036-06-30]
    D02A E491 73BD AD56 E4F8  8223 707E 56D3 DEF4 115C
    Ingo Klöcker (Release Signing Key 2026)

    brainpoolP256r1 2021-10-15 [SC] [expires: 2029-12-31]
    02F3 8DFF 731F F97C B039  A1DA 549E 695E 905B A208
    GnuPG.com (Release Signing Key 2021)

    brainpoolP384r1 2026-02-23 [SC] [expires: 2034-02-23]
    1493 269D E61F 124A A69A  316E 3ADF 34EB DBB2 00A4
    GnuPG.com (Release Signing Key 2026)

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

* Debian Package Signing Key:
  The new Debian style packages are signed using this key:

    ed25519 2025-07-08 [SC] [expires: 2035-07-14]
    3209 7B71 9B37 45D6 E61D DA1B 85C4 5AE3 E1A2 B355
    GnuPG.org Package Signing Key <[email protected]>

  See the package website (https://repos.gnupg.org/deb/gnupg) for a list
  of supported distributions and a download link for the key.

-- 
Arguing that you don't care about the right to privacy because you have
nothing to hide is no different from saying you don't care about free
speech because you have nothing to say.                - Edward Snowden

Attachment: openpgp-digital-signature.asc
Description: PGP signature

Reply via email to