{"id":5747,"date":"2024-06-29T11:28:58","date_gmt":"2024-06-29T03:28:58","guid":{"rendered":"http:\/\/blog.coolcoding.cn\/?p=5747"},"modified":"2024-06-29T11:30:59","modified_gmt":"2024-06-29T03:30:59","slug":"use-multiple-ssh-keys-for-git-host-websites-github-gitlab","status":"publish","type":"post","link":"https:\/\/blog.coolcoding.cn\/?p=5747","title":{"rendered":"Use Multiple SSH Keys for\u00a0Git\u00a0host websites (Github, Gitlab)"},"content":{"rendered":"\n

This is guide about how to configure multiple SSH<\/em> keys for some Git<\/em> host websites such as Github<\/em>, Gitlab<\/em>, among others.<\/p>\n\n\n\n

Creating SSH keys<\/h2>\n\n\n\n
    \n
  1. Create SSH<\/em> directory:mkdir ~\/.ssh<\/li>\n\n\n\n
  2. Move to created directory:cd ~\/.ssh<\/li>\n\n\n\n
  3. To create a SSH<\/em> key, type:ssh-keygen -t rsa -C “EMAIL@HOST.com”a message will be displayed:Generating public\/private rsa key pair. Enter file in which to save the key (\/home\/USER\/.ssh\/id_rsa):You should type someething of the default name of the file to distinguish service, such as: id_rsa_myaccount_github<\/code>, id_rsa_myaccount_gitlab<\/code>, id_rsa_mycompanyaccount_gitlab<\/code>.After this step a passphrase<\/em> is needed for security, which can be empty.<\/li>\n\n\n\n
  4. Repeat previous step for every required account.<\/li>\n\n\n\n
  5. To see if the keys were successful created:ls ~\/.sshwhich it is going to print all key files, for example: id_rsa_myaccount_github id_rsa_myaccount_gitlab.pub id_rsa_myaccount_github.pub id_rsa_mycompanyaccount_gitlab id_rsa_myaccount_gitlab id_rsa_mycompanyaccount_gitlab.pub<\/code><\/li>\n<\/ol>\n\n\n\n

    Creating config<\/em> file for manage SSH<\/em> keys<\/h2>\n\n\n\n
      \n
    1. To create config<\/code> file:touch ~\/.ssh\/config<\/li>\n\n\n\n
    2. Edit the file to configure domains<\/em> for the keys:nano ~\/.ssh\/configfor example, if three accounts were added, should look like this:# github account Host github.com HostName github.com PreferredAuthentications publickey IdentityFile ~\/.ssh\/id_rsa_myaccount_github # gitlab account Host gitlab.com HostName gitlab.com PreferredAuthentications publickey IdentityFile ~\/.ssh\/id_rsa_myaccount_gitlab # gitlab company account Host gitlab.my_company.com HostName gitlab.my_company.com PreferredAuthentications publickey IdentityFile ~\/.ssh\/id_rsa_mycompanyaccount_gitlab<\/code><\/li>\n\n\n\n
    3. Save file and exit.<\/li>\n<\/ol>\n\n\n\n

      Using two accounts from the same server (website) [Optional]<\/h3>\n\n\n\n

      A new host has to be created.<\/p>\n\n\n\n

        \n
      1. Create a new entry on the ~\/.ssh\/config<\/code> file(example with Github<\/em>):<\/li>\n<\/ol>\n\n\n\n
        Host other.github.com\nHostName github.com\nPreferredAuthentications publickey\nIdentityFile ~\/.ssh\/id_rsa_otheraccount_github<\/code><\/pre>\n\n\n\n
        where other.github.com<\/code> is the alias for the host, although the server(HostName<\/code>) is github.com<\/code>. The IdentityFile<\/code> option points to a (previously) created key file configured with the required account.<\/p>\n\n\n\n
        After this, a custom url can be used to clone the project.git clone git@other.github.com:USER\/REPOSITORY.git<\/p>\n\n\n\n
        where other.github.com<\/code> is the previously created domain.<\/p>\n\n\n\n
        Configure SSH<\/em> on Repository site<\/h2>\n\n\n\n
        To configure ssh on each repository website:<\/p>\n\n\n\n
          \n
        1. Copy the content of the id_rsa_X.pub<\/code> with xclip<\/code> command(may not be installed) to the clipboard(where id_rsa_X.pub<\/code> is the wanted key file):xclip -sel clip < ~\/.ssh\/id_rsa_X.pub(content also can also be manually copied from the *.pub<\/code> file)<\/li>\n\n\n\n
        2. Paste the content on the repository site, check next section.<\/li>\n<\/ol>\n\n\n\n
          Configure SSH<\/em> on Github<\/h3>\n\n\n\n
            \n
          1. Go to https:\/\/github.com<\/a>.<\/li>\n\n\n\n
          2. Go to Profile Settings<\/em> > SSH and GPG Keys<\/em> > click on button New SSH Key<\/em>.<\/li>\n\n\n\n
          3. On Title<\/em> add a descriptive label, such as the hostname<\/em> of the device\u2026\u200b<\/li>\n\n\n\n
          4. On the Key<\/em> field past the clip content with the key.<\/li>\n\n\n\n
          5. Finally click on Add SSH key<\/em> and after that the site ask for the user password.<\/li>\n<\/ol>\n\n\n\n
            Configure SSH<\/em> on Gitlab<\/h3>\n\n\n\n
              \n
            1. Go to https:\/\/gitlab.com<\/a>.<\/li>\n\n\n\n
            2. Go to Profile Settings<\/em> > SSH Keys<\/em>.<\/li>\n\n\n\n
            3. On the Key<\/em> field past the clip content with the key.<\/li>\n\n\n\n
            4. On Title<\/em> add a descriptive label, such as the hostname<\/em> of the device\u2026\u200b<\/li>\n\n\n\n
            5. Finally click on Add key<\/em>.<\/li>\n<\/ol>\n\n\n\n
              Testing SSH Keys<\/h2>\n\n\n\n
                \n
              1. Type(substitute HOST<\/code> with the desired one(github<\/em>, gitlab<\/em>, \u2026\u200b)):ssh -T git@HOST.coma warning will appear, accept it with yes<\/code>:The authenticity of host 'HOST.com (IP ADDRESS)' can't be established. RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48. Are you sure you want to continue connecting (yes\/no)?<\/code>A successful message will appear:\n
                  \n
                1. For Github<\/em>:Hi USERNAME! You've successfully authenticated, but GitHub does not provide shell access.<\/code><\/li>\n\n\n\n
                2. For Gitlab<\/em>:Welcome to GitLab, USERNAME!<\/code><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n\n\n\n
                  Delete SSH<\/em> Cache and add Keys<\/h3>\n\n\n\n
                  If the SSH<\/em> does not work, maybe the keys need to be added with ssh-add<\/code> command<\/p>\n\n\n\n
                    \n
                  1. First delete keys cache:ssh-add -Dif a message appear:Could not open a connection to your authentication agent.use this command and after that retry:eval `ssh-agent -s`<\/li>\n\n\n\n
                  2. Add key file with ssh-add<\/code> command:ssh-add ~\/.ssh\/id_rsa_file<\/li>\n\n\n\n
                  3. To see added keys, type:ssh-add -ldand something such as this will be displayed:2048 SHA256:DXlgYQo1o\/65JQCSYQo\/L4RRP4i+wTouyEetkOIcn\/o EMAIL_1 (RSA) 2048 SHA256:4FPtZYDtHipZeHqP9KNB3Wslz9L5q\/JoAGT3g\/NW3O8 EMAIL_2 (RSA) 2048 SHA256:tXCoBI2dMtTFhUhE5oBT+XwwkrhkorkOHbSc1J22urQ EMAIL_3 (RSA)<\/code><\/li>\n\n\n\n
                  4. Retry testing connection.<\/li>\n<\/ol>\n\n\n\n
                    Using SSH keys<\/h2>\n\n\n\n
                    To use a git repository with the SSH<\/em>, this url style has to be used for the repository:git@HOST:USERNAME\/REPOSITORY.git<\/p>\n\n\n\n
                    where HOST<\/code> is the configured domain, which can be github<\/em>, gitlab<\/em> or a personalized one.<\/p>\n\n\n\n
                    If project origin is already configured with HTTPS, it has to be changed to the SSH url style (check next section).<\/p>\n\n\n\n
                    Warning<\/td>If you want to use the HTTPS url, other steps will be required.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                    Change HTTPS url to SSH url [Optional]<\/h3>\n\n\n\n
                      \n
                    1. List existing remotes in order to get the name of the repository:git remote -v<\/li>\n\n\n\n
                    2. Change remote url, substitute HOST for server domain or a previously create custom HOST:git remote set-url origin git@HOST:USERNAME\/REPOSITORY.git<\/li>\n<\/ol>\n\n\n\n
                      Note<\/td>It can be used the same method to change from SSH to HTTPS.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                      Important: About git config<\/code> user name<\/em> and email<\/em><\/h2>\n\n\n\n
                      In spite SSH<\/em> keys were configured for the access, the Git<\/em> user name<\/em> and email<\/em> need to be configured, because these will be associated to the commits<\/em>.<\/p>\n\n\n\n
                      To see actual configuration, type:git config –list<\/p>\n\n\n\n
                      If global user name<\/em> and email<\/em> were configured will be displayed at the beginning, if not, these values will not appear.<\/p>\n\n\n\n
                      Note<\/td>If the command was run on a repository and this one has a local user name<\/em> and email<\/em> configured, these values will be displayed at the end of configuration.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                      Configure user name<\/em> and email<\/em> on all repositories (globally)<\/h3>\n\n\n\n
                      Important<\/td>You may want to configure the most used user name<\/em> and email<\/em> globally, but watch out since every commit with not local configuration<\/em> will use these values.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                        \n
                      1. Go to the root directory of the repository.<\/li>\n\n\n\n
                      2. Type to configure user name<\/em>:git config –global user.name “YOUR NAME”<\/li>\n\n\n\n
                      3. Type to configure user email<\/em>:git config –global user.email “email@HOST.com”<\/li>\n\n\n\n
                      4. To see if the global<\/strong> fields were correctly configured, use the git config --list<\/code> command or check global Git<\/em> file.nano ~\/.gitconfigthis will display a section like:[user] name = YOUR NAME email = email@HOST.comNoteIf the user name<\/em> or the user email<\/em> were not configured this section will not appear.<\/li>\n<\/ol>\n\n\n\n
                        Configure user name<\/em> and email<\/em> on a unique repository (locally)<\/h3>\n\n\n\n
                          \n
                        1. Go to the root directory of the repository.<\/li>\n\n\n\n
                        2. Type to configure user name<\/em>:git config user.name “YOUR NAME”<\/li>\n\n\n\n
                        3. Type to configure user email<\/em>:git config user.email “email@HOST.com”<\/li>\n\n\n\n
                        4. To see if the global<\/strong> fields were correctly configured, use the git config --list<\/code> command or check local Git<\/em> file:nano .\/.git\/configthis will display a section like:[user] name = YOUR NAME email = email@HOST.comNoteIf the user name<\/em> or the user email<\/em> were not configured this section will not appear.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
                          This is guide about how to configure multiple SSH& […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/posts\/5747"}],"collection":[{"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5747"}],"version-history":[{"count":3,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/posts\/5747\/revisions"}],"predecessor-version":[{"id":5750,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/posts\/5747\/revisions\/5750"}],"wp:attachment":[{"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5747"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5747"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5747"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}