[Announce] GnuPG 2.1.3 released

Werner Koch wk at gnupg.org
Sat Apr 11 20:34:43 CEST 2015


The GnuPG Project is pleased to announce the availability of the
another release of GnuPG modern: Version 2.1.3.

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.  Since version 2 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:

- GnuPG "modern" (2.1) is the latest development with a lot of new
  features.  This announcement is about the first release of this

- GnuPG "stable" (2.0) is the current stable version for general use.
  This is what most users are currently using.

- GnuPG "classic" (1.4) is the old standalone version which is most
  suitable for older or embedded platforms.

You may not install "modern" (2.1) and "stable" (2.0) at the same
time.  However, it is possible to install "classic" (1.4) along with
any of the other versions.

Noteworthy changes in version 2.1.3

 * gpg: LDAP keyservers are now supported by 2.1.

 * gpg: New option --with-icao-spelling.

 * gpg: New option --print-pka-records.  Changed the PKA method to use
   CERT records and hashed names.

 * gpg: New command --list-gcrypt-config.  New parameter "curve"
   for --list-config.

 * gpg: Print a NEWSIG status line like gpgsm always did.

 * gpg: Print MPI values with --list-packets and --verbose.

 * gpg: Write correct MPI lengths with ECC keys.

 * gpg: Skip legacy PGP-2 keys while searching.

 * gpg: Improved searching for mail addresses when using a keybox.

 * gpgsm: Changed default algos to AES-128 and SHA-256.

 * gpgtar: Fixed extracting files with sizes of a multiple of 512.

 * dirmngr: Fixed SNI handling for hkps pools.

 * dirmngr: extra-certs and trusted-certs are now always loaded from
   the sysconfig dir instead of the homedir.

 * Fixed possible problems due to compiler optimization, two minor
   regressions, and other bugs.

A detailed description of the changes found in the 2.1 versions can be
found at https://gnupg.org/faq/whats-new-in-2.1.html .

Getting the Software

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

GnuPG 2.1.3 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/mirrors.html>.  Note that GnuPG is not available
at ftp.gnu.org.

On ftp.gnupg.org you find these files:

 ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.3.tar.bz2  (4762k)

This is the GnuPG source code compressed using BZIP2 and its OpenPGP

An experimental Windows installer for this version will be released next

This version fixes a lot of bugs found after the release of 2.1.2 but
there are still known bugs which we are working on.  Please check the
the bug tracker, https://wiki.gnupg.org, or mailing list archives for
known problems and workaround.

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

     gpg --verify gnupg-2.1.3.tar.bz2.sig gnupg-2.1.3.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 below 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.1.3.tar.bz2, you would run the command like this:

     sha1sum gnupg-2.1.3.tar.bz2

   and check that the output matches the next line:

091e69ec1ce3f0032e6b135e4da561e8d46d20a7  gnupg-2.1.3.tar.bz2

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:

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

  rsa2048/E0856959 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/33BD3F06 2014-10-29 [expires: 2016-10-28]
  Key fingerprint = 031E C253 6E58 0D8E A286  A9F2 2071 B08A 33BD 3F06
  NIIBE Yutaka (GnuPG Release Key) <gniibe 'at' fsij.org>

  rsa2048/7EFD60D9 2014-10-19 [expires: 2020-12-31]
  Key fingerprint = D238 EA65 D64C 67ED 4C30  73F2 8A86 1B1C 7EFD 60D9
  Werner Koch (Release Signing Key)

You may retrieve these files from a keyserver using this command

  gpg --keyserver hkp://keys.gnupg.net --recv-keys  \
                  249B39D24F25E3B6 04376F3EE0856959 \
                  2071B08A33BD3F06 8A861B1C7EFD60D9

The keys are also 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 using by a different key.


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


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


The file gnupg.info has the complete user manual of the system.
Separate man pages are included as well but they have not all the
details available as are the manual.  It is also possible to read the
complete manual online in HTML format at


or in Portable Document Format 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 search the GnuPG mailing
list archives or ask on the gnupg-users mailing lists for advise on
how to solve problems.  Many of the new features are around for
several years and thus enough public knowledge is already available.

You may also want to follow postings at https://gnupg.org/blob/.


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>.  For commercial support
requests we keep a list of known service companies at:


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


We have to thank all the people who helped with this release, be it
testing, coding, translating, suggesting, auditing, administering the
servers, spreading the word, and answering questions on the mailing

Since the start of the funding campaign in December several thousand
people have been kind enough to donate a total of 250000 Euro to support
this project.  In addition the Linux Foundation gave a grant of $ 60000
for 2015, Stripe.com and Facebook.com each pledged $ 50000 per year.

I am amazed by this superb and unexpected support for the GnuPG project.
This allowed us to continue the project, employ a second full time
developer, and gives us the resources to improve things which have been
delayed for too long.

Thank you all!



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

Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 180 bytes
Desc: not available
URL: </pipermail/attachments/20150411/a2b69b67/attachment-0001.sig>
-------------- next part --------------
Gnupg-announce mailing list
Gnupg-announce at gnupg.org

More information about the Gnupg-devel mailing list