@werner Is it clearer now if gcryptrnd will be removed or ported?

No response anymore, and we can not reproduce.

Assigning to Werner for "re 1."

I don't know if this ever landed. If not, please reopen. We now have a bug tracker that can do nice patch management, too :)

@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!

If we will ever do this, then only in conjunction with appropriate continuous integration tools that report on new warnings and progress. Closing here.

Nobody started to hack on it in two years, and buried in this bug report nobody will find it. If this is still a desirable task, a new ticket should be opened.

We don't use roundup anymore.

@werner What's the status here?

Is this still an issue?

So, the default change 7y ago and the world didn't end. Closing this.

@werner do you have any updates on this?

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?

By the way, when terminating pinentry with "kill -TERM ...", it shuts down correctly, while CTRL-C show "gpg: signal Interrupt caught ... exiting" and a corrupt screen layout that is reset when pressing RETURN, further confirming the above diagnosis.

The problem seems to be that the CTRL-C is sent to gpg, terminating it, but pinentry keeps running and interfers with the terminal. With "ps -j" we can verify that pinentry runs in the process group and session of gpg-agent, while gpg runs in its own process group within the shell session. So, the signal rightly goes to gpg.

Refile if problems with current versions.

We can do this with estream now.