[Announce] The fifth Beta for GnuPG 2.1 is now available for testing

Werner Koch wk at gnupg.org
Thu Jul 3 12:05:07 CEST 2014

I just released the fifth *beta version* of GnuPG 2.1.  It has been
released to give you the opportunity to check out new features and
to fix the bugs in the last beta.

  If you need a stable and fully maintained version of GnuPG,
  you should use version 2.0.25 or 1.4.18.

This versions is marked as BETA and as such it should in general not be
used for real work.  However, the core functionality is solid enough for
a long time and I am using this code base for a couple of years now.

What's new in 2.1.0-beta751 since beta442

 * gpg: Make export of secret keys work again.

 * gpg: Create revocation certificates during key generation.

 * gpg: Create exported secret keys and revocation certifciates with
   mode 0700

 * gpg: The output of --list-packets does now print the offset of the
   packet and information about the packet header.

 * gpg: Avoid DoS due to garbled compressed data packets. [CVE-2014-4617]

 * gpg: Screen keyserver responses to avoid importing unwanted keys
   from rogue servers.

 * gpg: The validity of user ids is now shown by default.  To revert
   this add "list-options no-show-uid-validity" to gpg.conf.

 * gpg: Print more specific reason codes with the INV_RECP status.

 * gpg: Cap RSA and Elgamal keysize at 4096 bit also for unattended
   key generation.

 * scdaemon: Support reader Gemalto IDBridge CT30 and pinpad of SCT
   cyberJack go.

 * The speedo build system has been improved.  It is now also possible
   to build a partly working installer for Windows.

Getting the Software

GnuPG 2.1.0-beta751 is available at


and soon on all mirrors <http://www.gnupg.org/mirrors.html>.  A patch
against the last beta is also available.

Please read the README file !

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 trusted version of GnuPG installed, you
   can simply check the supplied signature.  For example to check the
   signature of the file gnupg-2.1.0-beta751.tar.bz2 you would use
   this command:

     gpg --verify gnupg-2.1.0-beta751.tar.bz2.sig

   This checks whether the signature file matches the source file.
   You should see a message indicating that the signature is good and
   made by that signing key.  Make sure that you have the right key,
   either by checking the fingerprint of that key with other sources
   or by checking that the key has been signed by a trustworthy other
   key.  Note, that you can retrieve the signing key using the command

     finger wk ,at' g10code.com

   or using a keyserver like

     gpg --keyserver keys.gnupg.net --recv-key 4F25E3B6

   The distribution key 4F25E3B6 is signed by the well known key


 * If you are not able to use an old version of GnuPG, you have to verify
   the SHA-1 checksum.  Assuming you downloaded the file
   gnupg-2.1.0-beta751.tar.bz2, you would run the sha1sum command like this:

     sha1sum gnupg-2.1.0-beta751.tar.bz2

   and check that the output matches this:

3d6dd8a377775780626428d98dba80dbbc5c27ac  gnupg-2.1.0-beta751.tar.bz2


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


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.

Almost all mail clients support GnuPG-2.  Mutt users may want to use
the configure option "--enable-gpgme" during build time and put a "set
use_crypt_gpgme" in ~/.muttrc to enable S/MIME support along with the
reworked OpenPGP support.


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>.  We also have a dedicated
service directory at:


Maintaining and improving GnuPG is costly.  For more than a decade,
g10 Code GmbH, a German company owned and headed by GnuPG's principal
author Werner Koch, is bearing the majority of these costs.  To help
them carry on this work, they need your support.  See



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

Happy Hacking,

  The GnuPG Team

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/20140703/a302d609/attachment.sig>

More information about the Gnupg-announce mailing list