#ADD SSH KEY TO SOURCETREE SOFTWARE#
#ADD SSH KEY TO SOURCETREE WINDOWS#

DON'T click on Generate Key, leave that blank.ġ7. Open SourceTree and add your account with Auth Type: OAuth, Protocol SSH, then click on 'Connect Account'. Warning: Permanently added ',192.30.255.112' (RSA) to the list of known hosts.ġ6. RSA key fingerprint is SHA256:aaaaabbbbbcccccddddeeee.Īre you sure you want to continue connecting (yes/no/)? yes The authenticity of host ' (192.30.255.112)' can't be established. Go to an empty folder and clone your GitHub repo git clone Cloning into 'YourProject'. Add the SSH key to your GitHub account.ġ4. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_ed25519 in the command with the name of your private key file. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. Note: If you chose not to add a passphrase to your key, you should omit the UseKeychain line.ġ2. Open your ~/.ssh/config file, then modify the file, replacing ~/.ssh/id_ed25519 if you are not using the default location and name for your id_ed25519 key. If the file doesn't exist, create the file. > The file /Users/ you/.ssh/config does not exist.ġ0. Check to see if your ~/.ssh/config file exists in the default location. > Enter passphrase (empty for no passphrase): This accepts the default file location.ħ. Create a new SSH Key ssh-keygen -t ed25519 -C ' When you're prompted to 'Enter a file in which to save the key,' press Enter. ssh folder (ASSUMING YOU AREN'T USING ANY KEYS IN THERE!!) rm -rf. Search for 'git' and delete all the keys you find (assuming you aren't using those keys for any other things)Ĥ. Open the app called 'Keychain Access' on Mac.Ģ. Now you can have security of SSH and 2-Factor Authentication, and keep using your favorite Git GUI yay!!.ġ. This solution works for authenticating using SSH AND 2-Factor Authentication for SourceTree 4.0.2 on Mac. I found a good solution to this problem which I will outline for everybody below. I'm quite disappointed with this engineering decision, but even more so, the fact they haven't corrected what I along with most other people on this thread think is an obnoxious interference into how experienced developers work.I have great news. In fact, I've also signed up for a small corporate plan on GitHub and have moved most of my new work there instead of BitBucket, so that I can more effectively use GitHub Desktop or their GUI for Pull Request management, something prompted largely due to this irritation. But to be honest, until they restore an ability for me to use MY OWN NAMING CONVENTION for the dozens of ssh keys I have to deal with, I have no interest in giving them another chance. Good to know symlinks work, should I ever decide to give these guys a chance again. That's the reason I haven't come back here since my original post, until getting another message today from this thread and getting curious.

#ADD SSH KEY TO SOURCETREE SOFTWARE#

There should be a way to specify the location of an existing ssh key!Īnother option, and the one I chose, is to switch to Github Desktop, as I really don't like a software vendor who breaks existing, widely-expected intuitive behavior without warning, and then ignores customer complaints about it for months.

Not letting me use my existing ssh key is a recipe for losing me as a customer - I don't like being forced to change the way I work. If you aren't ready to clone a repository, click Skip Setup. Follow the prompts until you're done with the setup. Why can't I use the ssh key which I want to use? Why isn't this finding my default ssh key like all other programs I have which use ssh, including earlier versions of SourceTree. If you can't continue without generating an SSH key, select HTTPS to continue or see Set up an SSH key for more details about setting up SSH with Sourcetree. Now, I see no way to specify this key, it's not being found despite being in the normal location on Mac/Linux systems, and it seems the only way to use ssh is to generate a new ssh key - WHICH I DO NOT WANT TO DO.

I used to be able to use this with SourceTree.

Now, I get a message 'no key found', despite the fact I have ~/.ssh/id_rsa defined, it's in my agent and Apple keychain, and I can use this fine everywhere else. Before, I could pick one of my ssh keys (I have dozens, but mainly use one for work and another for personal Git repos) during setup. It seems there is some change to how the setup and configuration of SSH keys work.

#ADD SSH KEY TO SOURCETREE WINDOWS#

I'm on a new project where I have to collaborate with some people on Windows and suggested they use SourceTree, and wanted to re-install SourceTree on my macs so I could help them learn this by demonstration, as I have used this from time to time in the past. I normally use the command line git client to work with GitHub or BitBucket. I just rebuilt my laptop and iMac with clean installs of MacOS Sierra.

Add ssh key to sourcetree