[Announce] Libgcrypt 1.8.6 released
wk at gnupg.org
Mon Jul 6 16:39:31 CEST 2020
The GnuPG Project is pleased to announce the availability of Libgcrypt
version 1.8.6. This is a maintenance release.
Libgcrypt is a general purpose library of cryptographic building blocks.
It is used by GnuPG and many other programs. Libgcrypt does not provide
any implementation of OpenPGP, S/MIME, or other protocols. Thorough
understanding of applied cryptography is required to use Libgcrypt.
Noteworthy changes in version 1.8.6
* Bug fixes:
- Fix build problems on OpenIndiana et al. [#4818]
- Fix GCM bug on arm64 which troubles for example OMEMO. [#4986]
- Fix wrong code execution in Poly1305 ARM/NEON implementation.
- Detect a div-by-zero in a debug helper tool. [#4868]
- Use a constant time mpi_inv in some cases and change the order
mpi_invm is called. [#4869]
- Fix mpi_copy to correctly handle flags of opaque MPIs.
- Fix mpi_cmp to consider +0 and -0 the same.
* Other features:
- Add OIDs from RFC-8410 as aliases for Ed25519 and Curve25519.
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:
or gzip compressed:
In order to check that the version of Libgcrypt you downloaded is an
original and unmodified file please follow the instructions found at
<https://gnupg.org/download/integrity_check.html>. In short, you may
use one of the following methods:
- Check the supplied OpenPGP signature. For example to check the
signature of the file libgcrypt-1.8.6.tar.bz2 you would use this
gpg --verify libgcrypt-1.8.6.tar.bz2.sig libgcrypt-1.8.6.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 libgcrypt-1.8.6.tar.bz2, you run the command like this:
and check that the output matches the first line from the
You should also verify that the checksums above are authentic by
matching them with copies of this announcement. Those copies can be
found at other mailing lists, web sites, and search engines.
Libgcrypt is distributed under the terms of the GNU Lesser General
Public License (LGPLv2.1+). The helper programs as well as the
documentation are distributed under the terms of the GNU General Public
License (GPLv2+). The file LICENSES has notices about contributions
that require that these additional notices are distributed.
For help on developing with Libgcrypt you should read the included
manual and if needed ask on the gcrypt-devel mailing list.
In case of problems specific to this release please first check
<https://dev.gnupg.org/T4985> for updated information.
Please also consult the archive of the gcrypt-devel 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>. If you need commercial
support go to <https://gnupg.com> or <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 gcrypt-devel mailing list for
Maintenance and development of GnuPG is mostly financed by donations.
The GnuPG project currently employs two full-time developers and one
contractor. They all work exclusively on GnuPG and closely related
software like Libgcrypt, GPGME and Gpg4win.
We have to thank all the people who helped the GnuPG project, be it
testing, coding, translating, suggesting, auditing, administering the
servers, spreading the word, and answering questions on the mailing
Many thanks to our numerous financial supporters, both corporate and
individuals. Without you it would not be possible to keep GnuPG in a
good shape and to address all the small and larger requests made by our
Your GnuPG hackers
This is an announcement only mailing list. Please send replies only to
the gcrypt-devel'at'gnupg.org mailing list.
List of 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 three keys:
rsa2048 2011-01-12 [expires: 2021-12-31]
Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
Werner Koch (dist sig)
rsa2048 2014-10-29 [expires: 2020-10-30]
Key fingerprint = 031E C253 6E58 0D8E A286 A9F2 2071 B08A 33BD 3F06
NIIBE Yutaka (GnuPG Release Key) <gniibe 'at' fsij.org>
rsa3072 2017-03-17 [expires: 2027-03-15]
Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28
Andre Heinecke (Release Signing Key)
The keys are 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 by a different key.
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 227 bytes
Desc: not available
More information about the Gnupg-announce