![]() Ssh-keygen -t rsa -b 4096 -C -f id_rsa-client Your public key has been saved in ~/.ssh/id_rsa.pub. Your identification has been saved in ~/.ssh/id_rsa. ssh-keygen -t rsa -b 4096 -C -f id_rsaĮnter passphrase (empty for no passphrase): Let’s create two new pairs of SSH keys, one for personal use and the other one for the clients project. If we can’t use the same SSH key across multiple accounts (what makes perfect sense) the solution is to have multiple. Change the upstream URL of already existing repository.Add public keys to individual Bitbucket accounts.Luckily the solution is simple and it applies the same, not only to Bitbucket, but also to other popular version control hosting services like GitHub or GitLab. That’s right, I had this key already added under my personal account. ![]() ![]() It is time to create an account, clone the repo and smash some code! Not that easy - this is what I got when I tried to add my public SSH key to newly created account. I recently joined a new project whereby a version control repository is hosted on Bitucket. Multiple SSH keys for multiple Bitbucket/GitHub accounts ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |