Well that was easy. All down to Libkleo::Formatting::displayName

Should not be too complicated.

Part of the task is the plumbing for that in GPGME of course, I'm not sure if werner will do the core "C" part directly or if you could do this also. But first let's get it added to GnuPG.

This is due to access control for "extra" socket.
Fixed in T5062: gpg: error getting version from 'scdaemon': Forbidden.

Hi all, I have this issue in Win10 in correct installation. Si I am interested what can I do to repair this issue. GPG is working correctly, but Kleopatra's selfcheck show this issue. Thanks. Portug

OK I found a very interesting thing here, @werner and finally I can reproduce this problem:

That is a version of gpg4win which we don't support or even know about. Please ask at their support site. Sorry.

We do have an Italian translation but it is quite outdated:

Thanks for the report. Indeed, the convenient C99 feature of variable definition in a for statement does only work in recent gcc versions and thus it should not be used in GnuPG related code. (https://gnupg.org/faq/HACKING.html was out of sync with the version in gnupg's master repo which falsely stated that it is an allowed features.)

Hello Werner,

The name field is marked as optional but it is mandatory. This should be fixed.

Thinking that maybe the gcc version is too old I tried using instead CentOS gcc7 development environment (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5) (which doesn't come out of the box). This was an educated guess as c99 is only partially supported in gcc-4.8.5. I have now successfully built:
libgpg-error-1.39
libassuan-2.5.3
gpgme-1.14.0
using gcc 7.3.1. All make check tests have passed.

The json problem can be overcome by changing the configure line to:

Actually I don't use systemd unit to start gpg-agent (creating that service file in systemd and make it start automatically) but I run it manually within the script. Also the script has selfcheck not to run multiple gpg-agent like below:

You used custom options which did not pick up the proper libksba. Install libksba correctly then try again. Please direct further questions to the mailing list and please build the latest version 2.2.23 and not an arbitrary old version.

@werner can you confirm if the environment I provided will work with OpenSSH support fully implemented?

We encountered the same issue today, and below is the debug messages. It works as expected once we downgraded to 2.2.21. We're on Arch Linux.

Version 2 is a bit too unspecific. Which version of what software are you using. Which OS?

Good catch. Thank you.

Hi,
I corrected all the accents. I created a PR here https://github.com/gpg/gpg4win/pull/3

Any ideas? Is there any other info needed that could help move this along?