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.

Please note that due to vacation issues the signatures use the gnupg.com Brainpool based release key and some Linux distributions come with Brainpool removed from GnuPG.

The first ideas sounds best to me. Patches please to the mailing list.

ACK. P[ease add it also to 2.2.

What about rejected changes to "Key:"? Other this command would make it too easy to mess up the actual private key.