We are currently investigating another problem with a new feature. Thus things are delayed. Hopefully we get a new release this month (or at least a new gnupg 2.3 version to install on top of gpg4win).

Should go into 1.10 too

Firefox nicely shows the 3 NIST certificates from my Telesec card but not the important Brainpool certificate for eIDAS. It turns out that Firefox does not support Brainpool, despite that a patch has been provided 8 years ago. See https://bugzilla.mozilla.org/show_bug.cgi?id=943639 . Thus there is currently no way to use LibreOffice or Okular to signe PDFs because they rely on NSS.

With my patch I see the expected status message:

The problem seems to be that we don't return a status code with the
actual error via the --command-fd interface:

Fixed in 2.2 and master. Did a couple of manual tests using 2.2 on Linux. gpgsplit comes handy to add a couple more tag-3 packets (same algos or one patched to camellia for the negative test)

This also points out that the cipher algos and modes of the symmetric encrypted session key packets where never checked for compliance. We only checked the compliance of the bulk encryption cipher algo.

Has this been implemented?

I don't think that we need to fix things here. Important is that the WKD import uses a filter which imports only keys with the requested mail address. However, if a key with the same fingerprint already exists it will be merged.

It is unlikely that the tofu stuff will get into widespread use in the 2.2 version - if at all.

Fixed quite some time ago.

Fixed with commits
rGeb675fbc4e4db52c3276bc0748b49df8a213fbc4
rG890e616593af5d1e0f2eb932768205ef90928e5e

The referenced bug should have been T6063

In de-vs mode we could change the implict algorithm from SHA-1 to SHA-256. That should solve the problem.

Backported for for 2.2.37

Fix will go into 2.2.37 and 2.3.8.

Probably fixed meanwhile in 2.2.
Please re-open if experience this problem also with a decent gnupg 2.2 versions.

Probably an invalid specified keyserver

That is not easy to change because we show all kind of error codes. If you run in --verbose mode you should see more info.

There won't be any semantic changes for obvious reasons.

Thanks for reporting.

The first thing is a problem of the GNU makeinfo tool. Can't be fixed int the source.