The primary value propositions of WSL is that you can have both Linux AND Windows. The problem is that the Linux distro you install in WSL see’s itself as it’s own operating system, and it wants its own set of SSH keys. There’s a good reason for that.Īn SSH key is specific to a machine.
I mention in that section that you can share SSH keys between Windows and WSL, but I never showed exactly how to do it. One of the things that I cover in that article is how to get SSH setup in WSL with Github. If you don't want to enter the key or password everytime, the easiest way is not to encrypt it.I recently wrote an article for Smashing Magazine that covers how I set up my personal development environment to use the Windows Subsystem for Linux version 2 (WSL 2).
If you need an encrypted ssh-key, you have to ssh-add the key everytime you reboot, as ssh-add lasts as long as your session. If you did, you have to make sure the ssh-agent is running and make sure you add the private key: $ eval `ssh-agent` There is no need to do ssh-add unless you set up a password for the keys. Verify everything is working as expected with ssh -T ssh keys:.Copy the contents of ~/.ssh/id_rsa.pub into the "Key" field (use cat ~/.ssh/id_rsa.pub or open with a text editor, but make sure to copy everything from the file).Write a "Label" with a descriptive sentence ("User Tismon at Home Workstation", for ex.).Now you need to add the keys to your bitbucket settings:
(you can omit the password here by pressing enter when asked if you wish to simply use the key-pair without entering a decryption password each time you login)Īfter this, verify the keys are generated: $ ls -l ~/.ssh The steps for enabling ssh in bitbucket are the following: Did you follow the official documentation here: ? Bitbucked instructions:
0 kommentar(er)
