[Announce] GnuPG 2.2.33 (LTS) released

Tue Nov 23 13:22:33 CET 2021

Hello!

We are pleased to announce the availability of a new GnuPG LTS release:
version 2.2.33.  This release fixes a few minor problems and brings a
few new options to ease user support and large scale installations.

The LTS (long term support) series of GnuPG is guaranteed to be
maintained at least until the end of 2024.  See
https://gnupg.org/download/index.html#end-of-life

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 can be freely used, modified and distributed under the terms of
the GNU General Public License.

Noteworthy changes in version 2.2.33 (2021-11-23)
=================================================

  * gpg: New option --min-rsa-length.  [rG6ee01c1d26]

  * gpg: New option --forbid-gen-key.  [rG985fb25c46]

  * gpg: New option --override-compliance-check.  [T5655]

  * gpgconf: New command --show-configs.  [rG8fe3f57643]

  * agent,dirmngr: New option --steal-socket.  [rG6507c6ab10]

  * scd: Improve the selection of the default PC/SC reader.  [T5644]

  * gpg: Fix printing of binary notations.  [T5667]

  * gpg: Remove stale ultimately trusted keys from the trustdb.  [T5685]

  * gpgsm: Detect circular chains in --list-chain.  [rGc9343bec83]

  * gpgconf: Create the local option file even if the global file
    exists.  [T5650]

  * dirmngr: Make reading resolv.conf more robust.  [T5657]

  * gpg-wks-server: Fix created file permissions.  [rGf54feb4470]

  * scd: Support longer data for ssh-agent authentication with openpgp
    cards.  [T5682]

  * Support gpgconf.ctl for NetBSD and Solaris.  [T5656,T5671]

  * Silence "Garbled console data" warning under Windows in most
    cases.

  * Silence warning about the rootdir under Unices w/o a mounted /proc
    file system.

  * Fix possible build problems about missing include files.  [T5592]

  * i18n: Replace the term "PIN-Cache" by "Passswort-Cache" in the
    German translation. [rgf453d52e53]

  * i18n: Update the Russian translation.

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

  The provided Windows installer is now build against Libgpg-error 1.43
  and thus features versatile meta options for the config file.  For
  example, it is possible to read and use option values from the
  Registry or from environment variables.  More on this is in a not
  published written blog article.

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

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

GnuPG 2.2.33 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
<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.2.33.tar.bz2 (7068k)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.33.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.2.33_20211123.exe (4424k)
 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.33_20211123.exe.sig

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 3 will not be published.  Gpg4win users may
instead install this version on top of 3.1.16 or wait for Gpg4win 4.

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

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

     sha1sum gnupg-2.2.33.tar.bz2

   and check that the output matches the next line:

70053b799a79139e0e7889282805fc889dd22540  gnupg-2.2.33.tar.bz2
6bf876e04ba00bebb64dffe7d2224206521948a7  gnupg-w32-2.2.33_20211123.tar.xz
c67151e92fc82bd4138ef441dbeba61e9bf4de5f  gnupg-w32-2.2.33_20211123.exe

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

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

In case of build problems specific to this release please first check
https://dev.gnupg.org/T5641 for updated information.

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 until this year 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
lists.

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

Happy hacking,

   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 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 keys:

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

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

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

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

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.

--
Please read

  Nils Melzer: Der Fall Julian Assange

It is really important to know the background of the Assange case to
understand the massive perils to free journalism.  The book is right
now only available in German: https://dev.gnupg.org/u/melzerassang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-announce/attachments/20211123/ac760ce2/attachment.sig>