![]() ![]() ![]() In fact, if you add passwords to the dialog in the same order as you would in the shell to an ssh-add, this would work. Think of it this way - if you have a fresh shell in your system, and you just started ssh-agent up, and ran ssh-add, what are the password prompts that you get? For every such password prompt, Sourcetree will give you this dialog box. ![]() If you have multiple ssh private keys which have different passwords, Sourcetree will give you a password prompt for each password. However since I wanted the password to be there, I kept investigating why it wasn't accepting my ssh key password. If I remove the password from the ssh key, this prompt doesn't come up. In my case, the password that Sourcetree was asking for was for the ssh private key password. Re-install SourceTree using all the correct credentials, point to the right repository and such.Īfter all this, SourceTree asked for my GitHub credentials twice, with two different dialog boxes, then stopped and worked! No more endless loop. Make sure your GitHub is setup the way you desire (for me, I also created and saved an SSH key that I used for SourceTree setup). ![]() Go up one level to ".\Local" and delete the "Atlassian" folder as well. I eventually ended up at "C:\Users\myusername\AppData\Local\SourceTree". Mine forked at "C:\Users\myusername\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Atlassian" where the shortcut pointed to another shortcut. The non-obvious bit was needing to delete the actual program files manually.įrom any "SourceTree.exe" shortcut, open file location. I setup SourceTree first and just clicked all the "setup later" options.Īn easy fix - Uninstall and re-install SourceTree. I also really feel like you should use a password.The problem for me seemed to be the order of setup between SourceTree and GitHub. No, I said "The more likely." as in a different situation. So if i get the pulse audio equalizer from anywhere, even if it turns out to be the fake-malicious one, it's going to ask my password to do the malicious thing then? So that means I'm safe everywhere until i type my password in to give the permission? So if i get the pulse audio equalizer from anywhere, even if it turns out to be the fake-malicious one, it's going to ask my password to do the malicious thing then? So that means I'm safe everywhere until i type my password in to give the permission? (Of course I don't count the first type-in, which makes the app installed, or the repository added) If something "bad" gets through and you're using a system that doesn't ask you the root password for installing and modifying stuff, then the "bad" stuff doesn't get asked it either and can much more than it would with normal user privileges. The more likely situation that people are trying to warn you about, is using your browser for example. How can i know if that's a trusted one, is there a mechanism like community controls the stuff and approves it or is it possible to get malicious software by typing "sudo apt get something" and then typing my password to start installation? Looks like each from different suppliers. There are different command strings on the web. So how i'm going to trust the software/packages that i install? For example i want to install pulseaudio equalizer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |