-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: None
-
Environment:From STSP-4810:
"n the SourceTree Tools > Options > SSH Client Configuration section, there is a drop-down that allows me to select PuTTY / Plink or OpenSSH. I'm trying to use OpenSSH as I'm using the ssh-agent.exe utility to authenticate in the terminal. However, what I'm realizing is that SourceTree doesn't honor the SSH_AGENT_PID and SSH_AUTH_SOCK environment variables to see if there is already an agent running. It will always launch a new instance of the agent and I will therefore have to enter my passphrases again into that agent.
There is a checkbox below that drop-down that says "Automatically start SSH agent when SourceTree opens". I would un-check that, but it's grayed out. Is there any way to get SourceTree to use the ssh-agent.exe that's already running?
BTW, the ssh-agent.exe is the one provided by the Git for Windows project."
We should honor an already running PID of their SSH agent when connectingFrom STSP-4810: "n the SourceTree Tools > Options > SSH Client Configuration section, there is a drop-down that allows me to select PuTTY / Plink or OpenSSH. I'm trying to use OpenSSH as I'm using the ssh-agent.exe utility to authenticate in the terminal. However, what I'm realizing is that SourceTree doesn't honor the SSH_AGENT_PID and SSH_AUTH_SOCK environment variables to see if there is already an agent running. It will always launch a new instance of the agent and I will therefore have to enter my passphrases again into that agent. There is a checkbox below that drop-down that says "Automatically start SSH agent when SourceTree opens". I would un-check that, but it's grayed out. Is there any way to get SourceTree to use the ssh-agent.exe that's already running? BTW, the ssh-agent.exe is the one provided by the Git for Windows project." We should honor an already running PID of their SSH agent when connecting
- relates to
-
SRCTREEWIN-1430 Check to see if SSH-Agent is already running
- Closed