visual studio code ssh keeps asking for password

To check if your public key is loaded into Bitbucket, do the following:įrom Bitbucket, choose Personal settings from your avatar in the lower left. Your public key isn't loaded into Bitbucket You shouldn't use sudo when cloning, pushing, or pulling because the ssh-agent runs on the user level, not the root level. You used sudo when attempting the connection Here are the most common reasons why you may see these messages: When attempting to clone, push, or pull over SSH with Git, you may receive one of these messages if Bitbucket couldn't authenticate with the keys that your SSH agent offered. You may see the following error messages when trying to authenticate over SSH. From a repository in Sourcetree, you can find the command line by clicking Terminal in the top right. However, you may need to using the command line for others. If you're using Sourcetree, some of these solutions come with Sourcetree steps. The prompt for root access did not exist when I wrote this answer.If you're having problems with SSH, here are some things you can try when troubleshooting your issues. The absolute best thing to do to is make a copy of a restricted file, edit it, and copy it back when you're absolutely sure it's finished.Īlso for editing files to which your user does not have permissions, I would now recommend Talha Junaid's answer which asks for permissions every single time you want to save a file. I'm not saying that you should never use VSCode as root(though its pretty easy to avoid doing) I'm saying you should be careful when you want to do so and know the risks. It's just good practice on any operating system to run your applications on a user level and leave administrative tasks to the root user, and only on a per-need basis. Or that vulnerability that was just posted in ProFTPD to allow an attacker to gain a ROOT shell. For example, you wouldn't want that recent crash of Rhythmbox to wipe out your entire /usr directory due to a bug.

Applications are meant to be run with non-administrative security (or as mere mortals) so you have to elevate their privileges to modify the underlying system. It defeats the security model that's been in place for years.

Have fun.įor everyone asking why this isn't recommended, you clearly don't understand why sudo even exists. Then from the window you can open your project folderĪgain: This is not recommended. You must specify the user data directory to use when running vs code: sudo code -user-data-dir='~/.vscode-root' It is very dangerous to run VScode as root (as it is any other application) however, should you absolutely need to:

Visual studio code ssh keeps asking for password