How to use correct key when I have multiple for github.com about wsl-ssh-agent HOT 4 CLOSED

This question is not related to wsl-ssh-agent...

You did not put your keys into windows ssh-agent service (using ssh-add). Instead, you are reading them directly from files judging from your configuration IdentityFile ~/.ssh/jibbers42-ed25519 and IdentityFile ~/.ssh/work-ed25519. As such wsl-ssh-agent has nothing to read from ssh-agent on windows end and make available on WSL2 side.

This could be easily verified by issuing ssh-add -L on both Windows side and WSL2 side and comparing results.

from wsl-ssh-agent.

I apologize for being off topic - I just hoped it was something someone here had experience with already since the WSL2 to Windows SSH agent would be out of experience for most people.

My thought was that the IdentityFile ... configuration told ssh which key to use, but it still used ssh-agent for credentials (I don't really know how it works). My keys have a passphrase that I am not prompted for so I'm sure I added them to ssh-agent and it's being used.

Both sides have the same ssh-add -L output...

Windows:

> ssh-add -L
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIK3E+1ehmyyQjfmDQ0a05L3jNvl+R3YskXZJCpPZxMGN work-ed25519
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAZHEf5lVMNMUFtOmlHKl76nOtCKY433nFqiNT22PE6m jibbers42-ed25519

WSL2:

$ ssh-add -L
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIK3E+1ehmyyQjfmDQ0a05L3jNvl+R3YskXZJCpPZxMGN work-ed25519
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAZHEf5lVMNMUFtOmlHKl76nOtCKY433nFqiNT22PE6m jibbers42-ed25519

from wsl-ssh-agent.

For anyone else that runs into this, I copied my ssh keys and .ssh\config to the WSL2 side. Since the config uses tilde for paths, the same paths work from both Windows and WSL2 and didn't need to be fixed up in any way. Now the correct key is being used from both sides and ssh-agent on Windows is authenticating everything.

from wsl-ssh-agent.

Agreed, this is as confusing as it could be... If you copied both keys and config - you may not need wsl-ssh-agent at all :) Not sure but in the future something like this: https://www.openssh.com/agent-restrict.html may be useful in such cases....

from wsl-ssh-agent.