-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssh-agent is ignored when with "IdentitiesOnly yes" config file setting #1550
Comments
I'm also having this issue on Windows 10. If I leave out If I then add say 15 identities to the config file without Is this being worked on at all? |
I have also just encountered this issue. Any update? |
Anybody home?? |
Hey, I have exactly the same issue. There is a high possibility that this is by design... From man: Specifies that ssh(1) should only use the authentication identity files configured in the ssh_config files, even if ssh-agent(1) offers more identities. The argument to this keyword must be ''yes'' or ''no''. This option is intended for situations where ssh-agent offers many different identities. The default is ''no''. I have found a nice post on superuser.com. Also, the workaround would be: replace The mystery is: why does the config ignore |
To me, this does not necessarily imply that ssh could not also ask ssh-agent for those authentication identity files which are configured (unless there is a technical hurdle that I am overlooking).
Which may very easily happen due to #1487. |
In linux OpenSSH, i have 6+ keys in the ssh-agent, which usualy is too many. So i use OpenSSH man page:
|
"OpenSSH for Windows" version
8.1.0.0
Server OperatingSystem
Linux
Client OperatingSystem
Windows 10 Pro
What is failing
When using
IdentitiesOnly yes
in an SSH config,ssh.exe
always asks for the encryption key of a an encrypted authentication key, even ifssh-agent
andAddKeysToAgent yes
is set in the same config files (even though the key is added to the agent).I do not think this is intended behavior.
This behavior has been described in #1133 (comment), but that issue has been closed, probably because there were a host of tangent issues discussed.
Expected output
The key should be obtainted from the
ssh-agent
.Actual output
It is not.
The text was updated successfully, but these errors were encountered: