Hello!
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.2
The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication
and data storage. It is a complete and free replacement of PGP and
can be used to encrypt data and to create digital signatures. It
includes an advanced key management facility and is compliant with the
proposed OpenPGP Internet standard as described in RFC2440.
Getting the Software
Please follow the instructions found at http://www.gnupg.org/download/
or read on:
GnuPG 1.4.2 may be downloaded from one of the GnuPG mirror sites or
direct from ftp://ftp.gnupg.org/gcrypt/ . The list of mirrors can be
found at http://www.gnupg.org/mirrors.html . Note, that GnuPG is not
available at ftp.gnu.org.
On the mirrors you should find the following files in the *gnupg*
directory:
gnupg-1.4.2.tar.bz2 (2.8M)
gnupg-1.4.2.tar.bz2.sig
GnuPG source compressed using BZIP2 and OpenPGP signature.
gnupg-1.4.2.tar.gz (4.0M)
gnupg-1.4.2.tar.gz.sig
GnuPG source compressed using GZIP and OpenPGP signature.
gnupg-1.4.1-1.4.2.diff.bz2 (939k)
A patch file to upgrade a 1.4.1 GnuPG source.
Select one of them. To shorten the download time, you probably want to
get the BZIP2 compressed file. Please try another mirror if
exceptional your mirror is not yet up to date.
In the *binary* directory, you should find these files:
gnupg-w32cli-1.4.2.exe (1.4M)
gnupg-w32cli-1.4.2.exe.sig
GnuPG compiled for Microsoft Windows and OpenPGP signature.
Note that this is a command line version and now comes with a
graphical installer tool. The source files are the same as
given above.
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-1.4.2.tar.bz2 you would use this command:
gpg --verify gnupg-1.4.2.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 "finger wk
'at' g10code.com" or "finger dd9jn 'at' gnu.org" or using the
keyservers. From time to time I prolong the expiration date; thus
you might need a fresh copy of that key.
Never use a GnuPG version you just downloaded to check the
integrity of the source - use an existing GnuPG installation!
* 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-1.4.2.tar.bz2, you would run the sha1sum command like this:
sha1sum gnupg-1.4.2.tar.bz2
and check that the output matches the first line from the
following list:
6eda5b090f9f1ac0da5e8b545e2667220a0e89ca gnupg-1.4.2.tar.bz2
cc7e9a5268bf309ac652a7343b62dff8cfb68d38 gnupg-1.4.2.tar.gz
ca0180b5e5d6ee78c68c701f6ded2d9008bf7608 gnupg-1.4.1-1.4.2.diff.bz2
8394920be8d2daa764e94d4bd5869853a3f293b8 gnupg-w32cli-1.4.2.exe
Upgrade Information
===
If you are upgrading from a version prior to 1.0.7, you should run the
script tools/convert-from-106 once. Please note also that due to a
bug in versions prior to 1.0.6 it may not be possible to downgrade to
such versions unless you apply the patch
http://www.gnupg.org/developer/gpg-woody-fix.txt .
If you have any problems, please see the FAQ and the mailing list
archive at http://lists.gnupg.org. Please direct questions to the
gnupg-users@gnupg.org mailing list.
What's New
===
* New command "verify" in the card-edit menu to display
the Private-DO-3. The Admin command has been enhanced to take
the optional arguments "on", "off" and "verify". The latter may
be used to verify the Admin Pin without modifying data; this
allows displaying the Private-DO-4 with the "list" command.
* Rewrote large parts of the card code to optionally make use of a
running gpg-agent. If --use-agent is being used and a gpg-agent
with enabled scdaemon is active, gpg will now divert all card
operations to that daemon. This is required because both,
scdaemon and gpg require exclusive access to the card reader. By
delegating the work to scdaemon, both can peacefully coexist and
scdaemon is able to control the use of the reader. Note that
this requires at least gnupg 1.9.17.
* Fixed a couple of problems with the card reader.
* Command completion is now available in the --edit-key
