Mailing List Archive

[Announce] GnuPG 2.2.10 released
Hello!

We are pleased to announce the availability of a new GnuPG release:
version 2.2.10. This is a maintenance release; see below for a list
of fixed bugs.


About GnuPG
===========

The GNU Privacy Guard (GnuPG) is a complete and free implementation
of the OpenPGP standard which is commonly abbreviated as PGP.

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. 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.2.10
===================================-

gpg: Refresh expired keys originating from the WKD. [#2917]

gpg: Use a 256 KiB limit for a WKD imported key.

gpg: New option --known-notation. [#4060]

scd: Add support for the Trustica Cryptoucan reader.

agent: Speed up starting during on-demand launching. [#3490]

dirmngr: Validate SRV records in WKD queries.

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


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

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

GnuPG 2.2.10 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.10.tar.bz2 (6503k)
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.10.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.10_20180830.exe (3919k)
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.10_20180830.exe.sig

The source used to build the Windows installer can be found in the same
directory with a ".tar.xz" suffix. A new Gpg4win installer featuring
this version of GnuPG will be available soon.


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

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

sha1sum gnupg-2.2.10.tar.bz2

and check that the output matches the next line:

3e87504e2ca317718aa9b6299947ebf7e906b54e gnupg-2.2.10.tar.bz2
c67cde7dffc82d592dff8538ed1ac8c28cc7c33d gnupg-w32-2.2.10_20180830.tar.xz
682002bce9e45309179a09348df3b92a82bdc501 gnupg-w32-2.2.10_20180830.exe


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

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


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

If you used GnuPG in the past you should read the description of
changes and new features at doc/whats-new-in-2.1.txt or online at

https://gnupg.org/faq/whats-new-in-2.1.html

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

The chapters on gpg-agent, gpg and gpgsm include information on how to
set up the whole thing. 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.

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 check out <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
======

Maintenance and development of GnuPG is mostly financed by donations.
The GnuPG project currently employs one full-time developer and two
contractors. All work exclusively on GnuPG and closely related software
like Libgcrypt and GPGME.

We have to thank all the people who helped the GnuPG project, be it
testing, coding, translating, suggesting, auditing, administering the
servers, spreading the word, and answering questions on the mailing
lists.

Many thanks to our numerous financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good shape and 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.

p.p.s
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:

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

rsa2048 2014-10-29 [expires: 2019-12-31]
Key fingerprint = 46CC 7308 65BB 5C78 EBAB ADCF 0437 6F3E E085 6959
David Shaw (GnuPG Release Signing Key) <dshaw 'at' jabberwocky.com>

rsa2048 2014-10-29 [expires: 2020-10-30]
Key fingerprint = 031E C253 6E58 0D8E A286 A9F2 2071 B08A 33BD 3F06
NIIBE Yutaka (GnuPG Release Key) <gniibe 'at' fsij.org>

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)

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

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
Re: [Announce] GnuPG 2.2.10 released [ In reply to ]
On Thu 2018-08-30 15:46:08 +0200, Werner Koch wrote:

> We are pleased to announce the availability of a new GnuPG release:
> version 2.2.10. This is a maintenance release; see below for a list
> of fixed bugs.

thanks for this work!

I note that https://gnupg.org/ftp/gcrypt/gnupg/ does not list 2.2.10
yet, though the file is already there.

Can you make refreshing that index a part of the standard release
process? it would help automated tools that scan that directory looking
for new releases to pick up the new release.

--dkg
Re: [Announce] GnuPG 2.2.10 released [ In reply to ]
On Thu, 30 Aug 2018 16:26, dkg@fifthhorseman.net said:

> I note that https://gnupg.org/ftp/gcrypt/gnupg/ does not list 2.2.10
> yet, though the file is already there.

It is there.

> Can you make refreshing that index a part of the standard release
> process? it would help automated tools that scan that directory looking
> for new releases to pick up the new release.

There is a cron job for it. You simply checked too early or I sent the
announcement too early ;-)

# Create HTML index files for the FTP server
20 1-23/2 * * * root /etc/mk-ftp-index.html.sh


Salam-Shalom,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.