• For Ed25519 private key segfault: see T5267

• Please see T5262 if you want to build with Qt4.

• For build problems on Raspberry PI see T5251 for a patch

Looking at the backlog of pinentry-related issues, I don’t think that would warrant delaying further the release of pinentry-1.1.1, especially given that the last release was 3 years ago already. Remaining issues (most of them being stalled anyway) or feature requests can be postponed for a future pinentry-1.2.0.

Released

Noteworthy changes in Version 3.1.15 (unreleased)

(en) GpgOL: Fixed a critical issue since Gpg4win-3.1.12 where

the selection of "No Key" for a recipient could lead to arbitrary
keys selected instead. (T5223)

We are hoping to have at least a beta release soon with gcrypt 1.9 that we can put in a Gpg4win-4 beta.

If you encounter this error message when running gpgconf --list-options gpg:

gpgconf: Option gpgconf-gpg.conf, needed by backend GnuPG, is not absolute

please simply create an empty file /etc/gnupg/gpg.conf or wherever your global configuration files are expected ("gpgconf --list-dirs sysconfdir" shows it). Bug fixed with commit rG9f37d3e6f307a9

See T5192 for an updated release.

In a discussion we decided that we need a deadline for GnuPG 2.3.0 so that we finally release it.

Released on 2020-11-18

Note that if you run into problems with a smartcard you should run "gpg --card-status" once. GUI frontends usually do that and this is the reason why this regression was not detected. Will be fixed in 2.2.25 (T5140).

A fix has been released; see T5052.

3.1.12 was released on 2020-07-24.

Unfortunately this new release has a regression affecting users with non-ascii account names. See T5098.

See
https://lists.wald.intevation.org/pipermail/gpg4win-announce/2020-September/000089.html
for the fixed Gpg4win 3.1.13

A bug was reported against this version which could happen also to older versions of GnuPG 2.2. In case of a crash please apply the patch over at rG8ec9573e57866dda5efb4677d4454161517484bc or wait for 2.2.23

As a workaround please run

There seems to be a problem with Gnuk and thus Nitrokey tokens with 2.2.22. We are investigating this. See T5039.

Release done.