search for: ssh_auth_sock_onlygitkey

...enticating against the remote server, but to forward another one. ssh could have a `ForwardAgentSocket` option, which specifies a different socket, and defaults to `${SSH_AUTH_SOCK}`. whether it's feasible to evaluate variables in that option (so a user could put `Host * / ForwardAgentSocket ${SSH_AUTH_SOCK_ONLYGITKEYS}` in a git config) is up to the way the config file is handled. the option should be accepted by `-o` too. together with ssh-agent-filter, or by running separate agents for work and linux, this would solve the bug #1937 without further workarounds. [1] https://github.com/tiwe-de/ssh-agent-filter...