-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
Use correct socket path for linux #334
Use correct socket path for linux #334
Conversation
Hi @alinalexandru, |
You are right with the user id. Don't know if there could be done a user id check in entry point. |
@alinalexandru maybe we can introduce a new variable that will be set similar to this? |
That it's a good ideea, it might solve this issue for most of the linux users. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you update your solution with suggested in comments changes?
Yes, I will work on that today. |
Any updates on when this can be release? Great job @alinalexandru for the debug. Thank you very much, i am having this issue very often now and couldn't figure out what was happening. |
@davidalger could you review this PR? |
LG2M as well. Thanks for the efforts at guiding this one @ihor-sviziev. Going to merge it, and once I have a chance to verify on my Linux box over here and update the CL will tag a release. |
Fixes #331
I explained in ticket the reason to set the
SSH_AUTH_SOCK
environment variable