Replies: 1 comment
-
I went through a rabbit hole on this and here my final solution that works for me. I use the Open SSH agent service of windows, and added |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have been trying to set up Cmder to use ssh-agent for authentication, and so far it seems that Cmder itself is using it fine, but when I call git, it ignores ssh-agent entirely.
OS: Windows 11 (22H2)
SSH: OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3
Cmder, etc.: up to date
I have loaded a couple keys into ssh-agent, and running
ssh-add -l
returns the expected result, listing the loaded keys.When I run
ssh -v [email protected]
, the output includes the expected references to the loaded keys:This successfully completes and I get this message at the end:
So, this part is alright. However, if I try to use any git commands, it does not attempt any keys from ssh-agent. I changed
~cmder\vendor\git-for-windows\etc\gitconfig
so thatsshCommand = ssh -v -A
, to see verbose output. I also edited~cmder\vendor\git-for-windows\etc\ssh\ssh_config
adding this section:I also updated
~\.ssh\config
with this section:Now when I run
git clone [email protected]:borisgred/sda.git
I get the verbose output. I see these lines appear:It's definitely reading the configuration files.
The verbose output has no references to the keys stored in ssh-agent. So in the end I get
[email protected]: Permission denied (publickey).
And that's the end.What am I missing? How do I get git under Cmder to pay attention to ssh-agent?
Beta Was this translation helpful? Give feedback.
All reactions