Closed shokinn closed 1 year ago
Just to check, is this WSL 1 or WSL 2?
WSL 2.
I am experiencing the exact same behavior. Any update / resolution?
Looks like a duplicate of #33
Thanks @kohenkatz - it does look like this is a duplicate of #33 . Unfortunately WSL 2 doesn't have any AF_UNIX
type socket support, so using the named pipe with npiperelay is probably the best solution.
Hey there, I'm currently facing the issue no matter what I do, I always get an Connection refused by the ssh-agend inside of my WSL 2 instance.
Here what I did:
C:\wsl-ssh-pageant
C:\Tools\wsl-ssh-agent\wsl-ssh-pageant-amd64.exe --systray --wsl C:\wsl-ssh-pageant\ssh-agent.sock --verbose
)SSH_AUTH_SOCK
toSSH_AUTH_SOCK
ssh-add -l
Output inside of WSL:
Output from wsl-ssh-pageant-amd64 running on windows:
The strange thing is that I don't get any log messages that there was a try to connect to socket.
I also tried to put the socket file in different locations. No change of this behaviour.
Any Ideas where i'm doing mistakes?