1Pass not using correct SSH key
To start I am using WSL2 (Ubuntu) on Windows 10.
I followed this guide to send SSH requests in WSL to Windows 10 agent/1Password agent.
This has been going well for a bit but something weird has happened lately:
I have two SSH keys at the moment, one for work and one that is personal. The work SSH key is in my work 1Pass account through the company and I have that and my personal one in the SSH agent config. I have my work one set before it as I want it to try that one first.
In short I have been trying to SSH tunnel into a database for work, this has been having an issue where it seems to only try my Personal SSH key and then stops. Thus causing it to deny the key.
Command: ssh -L XXXXXXX:XXXX XXXXXX@XXXXX
I have tried with -A as a flag for the command as well, doesn't help anything.
Reason I suspect it is only trying the personal is when I take a look at known_hosts afterwards, it only has 1 entry with the personal key.
I have taken the personal key out of the SSH agent config, and ran ssh-add -l to verify that it was only reading the work key. This however still tried to use the personal key which it shouldn't even have access to at this point. The personal key is not in a private vault either.
Same thing when I try to clone something from gitlab, except for with git it will succeed and when I check the known_host again, it shows the personal key??
The personal key is Ed25519 and the work one is RSA. I don't know if this is a cause for some reason or another.
1Password Version: 8.10.18
Extension Version: Not Provided
OS Version: Windows 10
Browser: Chrome