Oh, my bad. Someone on IRC said it was a bug and I didn't look at any further details.

No, that is the convention used by gpgconf. See https://gnupg.org/documentation/manuals/gnupg/Format-conventions.html#Format-conventions:

Given that we have no TESTING status, the only way I can handle this is by keeping the ticket open and add the TESTING flag. Closing a bug which has not been tested is a bad idea.

Please be so kind and explain in more detail what you did.

Fixed. Thanks.

It fails the very same way:

@werner An open ticket should mean there is something that can be acted upon. Unless you are saying that we should actively look for regressions or should actively do more testing, this ticket should be closed now. There is plenty of peripheral information that will remind us of this ticket in case more issues resurface related to this change.

If this is gone in master, please close this bug. Thanks :).

Fixed in 273964798592cd479c111f47e8ce46d5b1999d6a.

https://files.gpg4win.org/Beta/current/

Issue seems to be gone in gpg (GnuPG) 2.1.22-beta75

Additional info: I tried setting up a reproducer without using a smartcard, and it fails with no secret key similar to earlier versions

seems this was fixed along the way, then. I only tested with 2.1.18.

I can't remember either. We should swicth back to mailing lists for such things.

Anyway we should not allow empty user ids.

Any updates / thoughts on how this might be fixed?

ping

Well, can you then please fix it?

Any update on this?

1.4 has build fixes for NetBSD. Thus I _assume_ this bug has been fixed.

Unlikely

GpgOL has even been revamped 2 times since then.

According to my checkout this is at

werner@trithemius.gnupg.org:/cvs/gph

But that has long gone. I need to see where to find a backup of that repo.

No way to test on El Capitain anymore. It works on Sierra.

We now have a GPGME feature to list packets:

Libgcrypt 1.6 reaches EOL in 7 days, so we won't fix it.

With the new rndjent as used with libgcrypt 1.8 under Windows rhis can be claimed as finished.

Solution has been given: Use "gpg.conf-1" for gpg 1.4

I have tested this and it appears to fix the leak of gpg-agent processes in virt-builder, thanks.

I commited a change which should fix this on Linux

Thanks for testing.

Well, this is a regression due to us creating creating /run/user/gnupg/ socket directories now on the fly. Thus there is no more need to create non-default home directories via gpgconf. Now, gpg-agent watches the socket file and terminates itself as soon as the socket file vanishes. Before that change the socket for a non-default home directory was created in the homedir itself and thus removing the homedir also removed the socket file and in turn gpg-agent terminated itself.

Confirmed that it now compiles ok on Fedora, thanks.

Thanks for the reminder. Fixed.
Note that LIBASSUAN_LIBS is not needed because it is already part of t_common_ldadd.

This is such a large change that I feel uneasy to close the bug before we know that there are no regressions. This Means we need to wait whether the next release will break.

For anyone following this bug, someone has worked out a (very awkward) workaround: https://stackoverflow.com/a/27689596/2505159

I'm still hitting this on Fedora. The patch is simple and was posted on the mailing list but apparently not incorporated into git:

No response anymore, and we can not reproduce.

Assigning to Werner for "re 1."

@werner Can we close this here?

@werner I can't find the gnu privacy handbook sources, although they are mentioned here: https://gnupg.org/documentation/guides.html

Thanks for the fast response!

we don't use GPG4Win anymore ... so, honestly I don't know - if you want I can verify that. Or you simply close the topic ...

We don't use roundup anymore.

Is this still an issue?

Is this still an issue with the latest version?

Is this still an issue?

I don't think we can do anything about slow startup times due to anti-virus software, sorry.

Is this still an issue?

According to Wikipedia, Live Meeting was discontinued. https://en.wikipedia.org/wiki/Microsoft_Office_Live_Meeting

Is this still an issue?

Is this still an issue?

It's not possible, unless you convince the Emacs developers to add special support for it. See http://lists.gnu.org/archive/html/emacs-devel/2012-12/msg00798.html.

I used this workaround for the years I accessed my mail over ssh and emacsclient.

In many cases, it's possible to make two connections (e.g. via ssh) to such a server, and in one of those connections explicitly do:

Justus, thank you for the response and your time. My apologies if I raised an issue in vain.