Download GnuPG 2.1.15

GnuPG stands for GNU Privacy Guard and is also often abbreviated to GPG. This is a collection of tools for securing communication flows and data. It can be used to encrypt data and create digital signatures, and to provide a framework for public key cryptography. It supports both OpenPGP and s/mime standards. For more information, please refer to this page. The developers have released GnuPG 2.1.15 with the following announcement:

GnuPG 2.1.15 released

Hello!

The GnuPG team is pleased to announce the availability of a new release of GnuPG modern: Version 2.1.15. See below for a list of new features and bug fixes.

Noteworthy changes in version 2.1.15

• gpg: Remove the –tofu-db-format option and support for the split TOFU database.
• gpg: Add option –sender to prepare for coming features.
• gpg: Add option –input-size-hint to help progress indicators.
• gpg: Extend the PROGRESS status line with the counted unit.
• gpg: Avoid publishing the GnuPG version by default with –armor.
• gpg: Properly ignore legacy keys in the keyring cache.
• gpg: Always print fingerprint records in –with-colons mode.
• gpg: Make sure that keygrips are printed for each subkey in –with-colons mode.
• gpg: New import filter “drop-sig”.
• gpgsm: Fix a bug in the machine-readable key listing.
• gpg,gpgsm: Block signals during keyring updates to limits the effects of a Ctrl-C at the wrong time.
• g13: Add command –umount and other fixes for dm-crypt.
• agent: Fix regression in SIGTERM handling.
• agent: Cleanup of the ssh-agent code.
• agent: Allow import of overly long keys.
• scd: Fix problems with card removal.
• dirmngr: Remove all code for running as a system service.
• tools: Make gpg-wks-client conforming to the specs.
• tests: Improve the output of the new regression test tool.
• tests: Distribute the standalone test runner.
• tests: Run each test in a clean environment.
• Spelling and grammar fixes.

A detailed description of the changes found in the 2.1 branch can be found at https://gnupg.org/faq/whats-new-in-2.1.html.

Please be aware that there are still known bugs which we are working on. Check and the mailing list archives for known problems and workarounds.