Fixed in master and 2.2

libassuan: Done
libksba: Done
npth: Done
ntbtls: Done
libgcrypt: Done

Oh, that is really old code dating back to dirmngr-1. There is only one user I will see whether I can replace it with the generic parser we have in http.c

Now that is funny c+p code. I vaporized it to just a few lines.

It seems that this part of the code was not finished. Unfortunately upstream of the dns code is unresponsive and thus we started to maintain the code base by ourselves. There is still an open question whether we should do that to the full extend, in which case we would integrate the code closer into the GnuPG framework with its own logging subsystems.

The correct technical term is OpenPGP Public Keyblock but I better shut up on the certificate vs. Public key(block) question.

I can only tell that the term "Certificate" is exactly what Kleopatra was trying to use consistently in the GUI. For Kleopatra it is also important because it tries to work with both X509 "certificates" and OpenPGP "public keys".

A bit tricky, but this would be good to use gpgrt-config by gpg-error.m4.
I say "tricky", because its name is gpg-error.m4 but it configure GPGRT_CONFIG to access to GPG_ERROR_CONFIG.

Did you have the chance to try it out with 3.1.4?

It might be good idea to provide libgcrypt.pc in libgcrypt 1.8.x for forward compatibility with libgpg-error 1.33.

Well, I changed my mind. Use of new gpgrt-config requires software update to introduce gpgrt.m4 and update of configure.ac to switch gpgrt from gpg-error, in standard way.
That's too much this time. It's good to defer this change.

Sorry, there is no good way, but only workaround in this case, because it is complicated and it is basically wrong thing to do it by composite device (in my opinion). I'll describe detail in this comment.
I'm not Windows user, so, I don't have an idea how to recover from such a situation.

OK, I'll change to use gpgrt-config, along with requiring newer version of libgpg-error.

Thanks

Thanks.

Thanks.

Thanks.

Thanks.

Thanks