Hello!
We are pleased to announce the availability of a new stable GnuPG-2.0
release: Version 2.0.30. This is a maintenance release which fixes a
couple of bugs.
The GNU Privacy Guard (GnuPG) is a complete and free implementation of
the OpenPGP standard as defined by RFC-4880 and better known as PGP.
GnuPG, also known as GPG, 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 including support for ECC. All new installations should use
that version.
- GnuPG "stable" (2.0) - which this is about - 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.
What's New in 2.0.30
===================
* gpg: Avoid too early timeout during key generation with 2.1 cards.
* agent: Fixed printing of ssh fingerprints for 384 bit ECDSA keys.
* agent: Fixed an alignment bug related to the passphrase
confirmation.
* scdaemon: Fixed a "conflicting usage" bug.
* scdaemon: Fixed usb card reader removal problem on Windows 8 and
later.
* Fixed a problem on AIX due to peculiarity with RLIMIT_NOFILE.
* Updated the Japanese and Dutch translations.
* Fixed a few other bugs.
Getting the Software
===================
Please follow the instructions found at https://gnupg.org/download/
or read on:
Source code is hosted at the GnuPG FTP server and its mirrors as listed
at <https://gnupg.org/download/mirrors.html>. On the primary server
the source tarball and its digital signature are:
ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.0.30.tar.bz2 (4311k)
ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.0.30.tar.bz2.sig
or here:
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.0.30.tar.bz2 (4311k)
https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.0.30.tar.bz2.sig
Note, that we don't distribute gzip compressed tarballs for GnuPG-2.
A Windows version will soon be released at <https://gpg4win.org>.
If you are new to GnuPG please use the "modern" version 2.1.11.
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.0.30.tar.bz2 you would use this command:
gpg --verify gnupg-2.0.30.tar.bz2.sig gnupg-2.0.30.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.0.29.tar.bz2, you would run the command like this:
sha1sum gnupg-2.0.30.tar.bz2
and check that the output matches the next line:
a9f024588c356a55e2fd413574bfb55b2e18794a gnupg-2.0.30.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 the keyservers using this command
gpg --recv-keys 249B39D24F25E3B6 04376F3EE0856959 \
2071B08A33BD3F06 8A861B1C7EFD60D9
using an already installed version of gpg. Remeber to check the
fingerprints against the above list (which you also find on the flip
side of our printed visit cards). The keys are also available at
<https://gnupg.org/signature_key.html> and in the released GnuPG tarball
in the file g10/distsigkey.gpg . Note that this mail has been signed
using my standard PGP key.
Documentation
============
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
https://www.gnupg.org/documentation/manuals/gnupg-2.0/
or in Portable Document Format at
https://www.gnupg.org/documentation/manuals/gnupg-2.0.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.
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>. For commercial support
requests we keep a list of known service companies at:
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.
Maintenance and development of GnuPG is mostly financed by donations.
We currently employ 3 full-time developers, one part-timer, and one
contractor. They all work on GnuPG and closely related software like
Enigmail. Please see
https://gnupg.org/donate/
on how you can help.
Thanks
=====
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
lists. Maintenance and development of GnuPG is possible due to many
individual and corporate donations; for a list of non-anonymous donors
see <https://gnupg.org/donate/kudos.html>.
For the GnuPG hackers,
Werner
p.s.
This is an announcement only mailing list. Please send replies only to
the gnupg-users 'at' gnupg.org mailing list.
--
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/20160331/5b103c0e/attachment-0001.sig>