Since Windows 10 1803, a built-in/optional OpenSSH implementation is included with Windows, including a SSH agent service. I've configured git to use this OpenSSH by adding this to my .gitconfig:
[core]
sshCommand = "C:/Windows/System32/OpenSSH/ssh.exe"
Sourcetree however, seems to only want to use either Pageant or the OpenSSH agent bundled with Git. Anyone know of a workaround, or do we just have to wait for Sourcetree to support the built-in OpenSSH implementation?
Hi
We have prototyped using the built in OpenSSH but ran into some issues around make sure it was available and running. We continue to monitor it and work on it, but it is not yet a roadmapped feature.
@minnseyHas there been any progress on this?
When I configure SourceTree to use OpenSSH it appears to start a new ssh-agent each time SourceTree is started and I receive the following error:
SourceTree is not the only way in which our teams interact with git via SSH. We also use the git cli directly, vscode, visual studio, Git Kraken, among others. It would be immensely helpful if SourceTree for Windows could use the same OpenSSH agent that Bitbucket's own documents mention.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ryan Taylor When your OpenSSH of windows setting is ok, then you no need the ssh client of SourceTree. Disable it and use the system git.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Leonswhen I do that, SourceTree is then configured to use PuTTY rather than OpenSSH and I receive errors on fetch and pull.
My OpenSSH configuration works flawlessly with
The only tool chain that seems to have issues with Windows' built-in OpenSSH is SourceTree.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SourceTree is not the only way in which our teams interact with git. We also use the git cli directly, vscode, visual studio, among others. It would be immensely helpful if SourceTree for Windows could use the same OpenSSH agent that even your own documents mention.
This could simplify setup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was able to accomplish this with the newly released winssh-pagent tool by setting Sourcetree to use Pageant auth and unchecking the "Start agent" box. See: https://github.com/ndbeals/winssh-pageant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Greetings!
Is this feature still considered for a future release?
In my new job I started using SourceTree, since it is the division policy, and I like it so far. However, I wish it could use Windows SSH-Agent, which I already successfully configured for the few instances when I do manual git commands.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Is there meanwhil an update when the feature will be available or at least on the roadmap?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.