When using GPG4Win 5-beta gpg-agent seems to crash when a connection to pagent is occuring.
After the update to GPG4Win 5-beta everyting seems to be fine connecting with windows own ssh works fine ssh-add -L shows the keys ( I have the keys on my Yubikey) but when trying to connect with putty it falls back to username password. Then the gpg-agent is also not running anymore and ssh -L doesn’t show the keys anymore. Reinstalling version 4.4.1 and all is good again. I tried this with version beta345 and beta357
I did activate some debugging.
The infos for the timestamps are .
16:30:30 launching gpg-connect-agent
16:30:40 ssh-add -L
16:30:50 launching a putty connection
simple ssh connection to same server works (not in logs)
I could only upload 2 log files so i omitted the file that only gave logs at 16:03:41 as no logs during end/crash
it is not fully clear to us yet what you are trying to do. obviously there’s two machines involved and you want to login from one to the other, correct? what is the setup on each of these machines (client/server; both windows? which version, also regarding the ssh tools involved)?
the crashes you are observing are happening on the client side, right? the problem is triggered by a specific ssh client then?
we need to be able to reliably replicate the issue in order to investigate what’s going wrong.
I have my key on yubikey in my laptop and usually connect to all devices where possible through an ssh connection. As ssh-agent I use the gpg-agent with pagent compatibility. (I have the same setup @home with linux as @work with Windows) This usually works like a charm. But with the GPG4win-beta’s it doesn’t. So I checked and I saw that in the Taskmanager the gpg-agent disappears at the very same moment when I launch an ssh connection. So i suppose that when the ssh client (here putty) connect through the pagent emulation to gpg-agent it crashes. Using the openssh socket through gpg-agent it works fine.
If you need any more input or information I am happy to provide them.
Here the content of the gpg-agent.conf of the client:
we were able to find and fix the problem. the fix is included in the just released GnuPG 2.5.12 which will be part of the next Gpg4Win beta release.
if you can’t wait, you can use the windows installer from the above announcement (“Getting the Software” section) and simply install it over the GnuPG version that came with Gpg4Win. make sure you restart all running daemons/agents after that (e.g., gpgconf.exe --kill all followed by gpgconf.exe --launch gpg-agent to re-enable ssh support).
