New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Windows SSH-Agent Deadlock issue #10
Comments
Hello Gary! thanks for the helpful bug report, and I'm glad you find this tool useful. Ohh joy this is going to be a fun one to fix 😅, interfacing with win32 api in go is always a nightmare. I'll look into it, can I get the code/binary for the custom SSH agent you're using, so that I may replicate this error and then test fixes. |
Poking through the forks, you've forked this and seemingly implemented a fix already: https://github.com/gazzenger/winssh-pageant Did you have plans to open a pull request? |
Awesome, I've gone and created a pull request, #11 Unrelated, but if you're interested, I've made some other commits, and moved the pageant.go file into it's own folder. This allows the package to be imported into other peoples code. |
Thanks for opening the pull request, I plan to merge it today. As for making pageant.go it's own pacakge, I'm cool with that, though I personally lack the imagination to see why others may want to use it, but that's on me. I'll end up pulling that one in a little later, feel free to open a PR for it too. Further discussion relating to PR #11 should be had in that PR, as I've got a few questions for you in it already. |
PR #11 merged, closing this. |
Hi Nathan,
I'm so glad I came across this repo, it does exactly what I need.
I've come across an issue when running winssh-pageant with my own custom SSH-Agent (this is running using the crypto/ssh/agent library)
I run my custom SSH-Agent, which allows connections using named pipes, and when I run winssh-pageant, this allows connections using PuTTY just fine.
But if I'm doing other things on my computer, after a little while, winssh-pageant always seems to crash with a deadlock.
From what I can find out about the error, it appears to be related to a nil pointer in the message loop, in the
main()
function.A really good explanation of I what I think the problem is, is detailed here
The full error stack for my issue is show below.
A few possible solutions I've found are listed below (I'm not sure if they would be a permanent fix, but they at least worked for me)
Suggesting to define
msg
as thisruntime.LockOSThread()
in themain()
function, I found this discussed hereThanks so much for putting together this repo, it's been really really helpful.
And many thanks for any help.
-Gary
The text was updated successfully, but these errors were encountered: