You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a somewhat fresh install of Windows 10 + WSL Ubuntu 20.04 (installed from the Windows App Store). The WinCryptSSHAgent worked perfectly using the WSL(1) version, not so much when using the WSL2 version.
Upon some light investigation, I noticed that the instructions attempts to point SSH_AUTH_SOCK to a file within /tmp/wincrypt-hv.sock, which is nonexistent even when rebooting the PC.
I'm not on the Windows-Insiders version, so I upgraded the distro to WSL2 manually and followed the new instructions showed on WinCryptSSHAgent: WSL2 / Linux on Hyper-V Settings only to find that something broke.
To Recreate
Install WinCryptSSHAgent via Chocolatey
Install "Ubuntu 20.04" (not "Ubuntu") from App Store
Found the culprit: Ubuntu didn't ship with socat by default so the file never got created, and it never seemed to complain because the output was fed into /dev/null
Overview
I'm using a somewhat fresh install of Windows 10 +
WSL Ubuntu 20.04
(installed from the Windows App Store). The WinCryptSSHAgent worked perfectly using the WSL(1) version, not so much when using the WSL2 version.Upon some light investigation, I noticed that the instructions attempts to point
SSH_AUTH_SOCK
to a file within/tmp/wincrypt-hv.sock
, which is nonexistent even when rebooting the PC.I'm not on the Windows-Insiders version, so I upgraded the distro to WSL2 manually and followed the new instructions showed on WinCryptSSHAgent:
WSL2 / Linux on Hyper-V Settings
only to find that something broke.To Recreate
wsl -l -v
ssh-add -l
ssh-add -l
The text was updated successfully, but these errors were encountered: