[Announce] GnuPG 2.2.7 released

[Werner Koch]

Hello!

We are is pleased to announce the availability of a new GnuPG release:
version 2.2.7.  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.7
===

  * gpg: New option --no-symkey-cache to disable the passphrase cache
for symmetrical en- and decryption.

  * gpg: The ERRSIG status now prints the fingerprint if that is part
of the signature.

  * gpg: Relax emitting of FAILURE status lines

  * gpg: Add a status flag to "sig" lines printed with --list-sigs.

  * gpg: Fix "Too many open files" when using --multifile.  [#3951]

  * ssh: Return an error for unknown ssh-agent flags.  [#3880]

  * dirmngr: Fix a regression since 2.1.16 which caused corrupted CRL
caches under Windows.  [#2448,#3923]

  * dirmngr: Fix a CNAME problem with pools and TLS.  Also use a fixed
mapping of keys.gnupg.net to sks-keyservers.net.  [#3755]

  * dirmngr: Try resurrecting dead hosts earlier (from 3 to 1.5 hours).

  * dirmngr: Fallback to CRL if no default OCSP responder is configured.

  * dirmngr: Implement CRL fetching via https.  Here a redirection to
http is explictly allowed.

  * dirmngr: Make LDAP searching and CRL fetching work under Windows.
This stopped working with 2.1.  [#3937]

  * agent,dirmngr: New sub-command "getenv" for "getinfo" to ease
debugging.


Getting the Software


Please follow the instructions found at  or
read on:

GnuPG 2.2.7 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
.  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.7.tar.bz2 (6475k)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.7.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.7_20180502.exe (3814k)
 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.7_20180502.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.7.tar.bz2 you would use this command:

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

 sha1sum gnupg-2.2.7.tar.bz2

   and check that the output matches the next line:

e222cda63409a86992369df8976f6c7511e10ea0  gnupg-2.2.7.tar.bz2
a00f7119c85dd837336f13be3174178d0cf8d85e  gnupg-w32-2.2.7_20180502.exe
46ac3b8e95f49a602c3f4b447803d80509867d11  gnupg-w32-2.2.7_20180502.tar.xz


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 des

Re: gpgsm --verify

[Stefan Claas]

Am 02.05.18 um 07:35 schrieb Werner Koch:

On Tue,  1 May 2018 10:55, stefan.cl...@posteo.de said:


openssl cms -verify -in original.eml > message.txt && \
openssl cms -cmsout -in original.eml | \
sed "1,4d" | base64 -d > file.sig && \
gpgsm --verify file.sig message.txt

Adding --verbose to the gpgsm invocation may give you additional hints.
IIRC, "--debug x509" may be helpful to.  Is file.sig a valid CMS file;
that is can you parse it with dumpasn1 or the openssl sub-command?

BTW, gpgsm has an option --assume-base64 so that you don't need the base64
tool.


Thank you very much for the additional information,
much appreciated!

Yes, file.sig can be parsed with dumpasn1.

Regards
Stefan

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users