WSL 2 setup about wsl-ssh-agent HOT 2 CLOSED

Dawid, WSL2 does not actually use wsl-ssh-agent-gui.exe, only npiperelay.exe, so it does not matter how you started it or how it is configured.

if you .bashrc is correct and you have installed socat on your WSL2 Linux distro - everything should just work even without you running wsl-ssh-agent-gui.exe from powershell. Socket is being created by socat, when accessed from the WSL2 end socat runs npiperelay.exe which accesses pipe and ssh-agent service on Windows end that it all you need. You could normally validate staff by running ssh-add -L from Windows and from WSL2 to see the same results.

Now - I have no udea what KeypassXC is, what it does and how you want it to be used.

from wsl-ssh-agent.

Thanks for such a quick response!

Well, okay, now I understand. Thanks for explaining.

Keepass (KeepassXC) is a simple password manager. While Keepass needs Keeagent (Plugin) to support ssh keys storage KeepassXC doesn't as this functionality is being natively delivered.

While I was on WSL1 I have imported my keys like that: https://gist.github.com/strarsis/e533f4bca5ae158481bbe53185848d49
and it was working fine.

I've tried running ssh-add -L from Windows and all of my ssh keys have showed up (that's what I expected) while on WSL2 following error occurred:
error fetching identities: communication with agent failed.

socat is installed. I don't think that I have messed up with my paths.

I've reinstalled my whole WSL and done all the steps before with leaving the gui thing.
Now ssh-add -L showed all of my keys and it is working. Thank you for your help!

from wsl-ssh-agent.