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. 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. 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. Stack Overflow Message 'Support for password authentication was removed.' Ask Question Asked 1 year, 11 months ago Modified yesterday Viewed 1.6m times 1506 I got this error on my console when I tried to use git pull: remote: Support for password authentication was removed on August 13, 2021. Click the Accounts tab, select the account where you want to add the SSH key and click. 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. Create an SSH key From the Sourcetree menu, select Preferences. 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. These versions of SourceTree fully support OAuth 2.0. 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. By Kelvin Yap on FebruConnect to your Bitbucket or GitHub accounts securely and with ease in the latest versions of SourceTree for Windows and Mac. It seems there is some change to how the setup and configuration of SSH keys work. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |