- Open Git Bash<\/li>
- paste the text below, substituting in your email address<\/li><\/ul>\n\n\n\n
$ ssh-keygen -t ed25519 -C \"your_email@example.com\"<\/code><\/pre>\n\n\n\nNote:<\/strong> If you are using a legacy system that doesn't support the \nEd25519 algorithm, use:<\/pre>\n\n\n\n
$ ssh-keygen -t rsa -b 4096 -C \"your_email@example.com\"<\/code><\/pre>\n\n\n\nThis creates a new ssh key, using the provided email as a label.<\/p>\n\n\n\n
> Generating public\/private ed25519 key pair.<\/code><\/pre>\n\n\n\nthe default file location is : <\/p>\n\n\n\n
\/c\/Users\/you\/.ssh\/id_ed25519<\/code><\/pre>\n\n\n\nAdding your SSH key to your Git-account<\/span><\/h5>\n\n\n\n
Copy the contents of the file
~\/.ssh\/id_ed25519.pub<\/code> ( in Windows: \/c:\/users\/you\/.ssh\/id_ed25519.pub) to your SSH keys in your Git account settings ( example: https:\/\/github.com\/settings\/keys<\/a>).<\/p>\n\n\n\nIn the upper-right corner of any page, click your profile photo, then click Settings<\/strong>.\n<\/pre>\n\n\n\n
![\"Settings](\"https:\/\/docs.github.com\/assets\/images\/help\/settings\/userbar-account-settings.png\")
<\/figure>\n\n\n\nIn the user settings sidebar, click SSH and GPG keys<\/strong>.\n\n
![\"Authentication](\"https:\/\/docs.github.com\/assets\/images\/help\/settings\/settings-sidebar-ssh-keys.png\")
<\/pre>\n\n\n\nClick New SSH key<\/strong> or Add SSH key<\/strong>.\n\n
![\"SSH](\"https:\/\/docs.github.com\/assets\/images\/help\/settings\/ssh-add-ssh-key.png\")
<\/pre>\n\n\n\nIn the \"Title\" field, add a descriptive label for the new key.\n For example, if you're using a personal Mac, you might call this\n key \"Personal MacBook Air\".\n\nPaste your key into the \"Key\" field.\n\n
![\"The](\"https:\/\/docs.github.com\/assets\/images\/help\/settings\/ssh-key-paste.png\")
<\/pre>\n\n\n\nClick Add SSH key<\/strong>.\n
![\"The](\"https:\/\/docs.github.com\/assets\/images\/help\/settings\/ssh-add-key.png\")
<\/pre>\n\n\n\nIf prompted, confirm your Git password.\n
![\"Sudo](\"https:\/\/docs.github.com\/assets\/images\/help\/settings\/sudo_mode_popup.png\")
<\/pre>\n\n\n\nTesting if work !!<\/span><\/h5>\n\n\n\n
Test SSH key:<\/p>\n\n\n\n
$ ssh -T git@github.com\nHi developius! You've successfully authenticated, but GitHub does not provide shell access.<\/code><\/pre>\n\n\n\nChange directory into the local clone of your repository (if you’re not already there) and run:<\/p>\n\n\n\n
git remote set-url origin git@github.com:username\/your-repository.git<\/code><\/pre>\n\n\n\nNow try editing a file (try the README) and then do:<\/p>\n\n\n\n
$ git commit -m \"Update README.md\"\n$ git push<\/code><\/pre>\n\n\n\nIf successful , you should not be asked for a username or password. Your SSH key is correctly configured.<\/p>\n\n\n\n
<\/p>\n\n\n\n
multiple ssh keys in .ssh folder?<\/span><\/h4>\n\n\n\n
Yes you can have different ssh keys. for different repository or even different git tools ( exple: gitlab & github).<\/p>\n\n\n\n
What you can do is set up a
~\/.ssh\/config<\/code><\/a> file in which you can associate the right private key with the right host, as explained here<\/a>.<\/p>\n\n\n\nI – Using multiple repositories on one server <\/span><\/h5>\n\n\n\n
In the server’s SSH configuration file (usually
~\/.ssh\/config<\/code>), add an alias entry for each repository. For example:<\/p>\n\n\n\nHost github.com-repo-0\n Hostname github.com\n IdentityFile=\/home\/user\/.ssh\/repo-0_deploy_key\n\nHost github.com-repo-1\n Hostname github.com\n IdentityFile=\/home\/user\/.ssh\/repo-1_deploy_key<\/code><\/pre>\n\n\n\nHost github.com-repo-0<\/code> – The repository’s alias.<\/li>Hostname github.com<\/code> – Configures the hostname to use with the alias.<\/li>IdentityFile=\/home\/user\/.ssh\/repo-0_deploy_key<\/code> – Assigns a private key to the alias.<\/li><\/ul>\n\n\n\nYou can then use the hostname’s alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example:<\/p>\n\n\n\n
$ git clone git@github.com-repo-1:OWNER\/repo-1.git<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"Create a new repository, or reuse an existing one. Generating a new SSH key Open Git Bash paste the text below, substituting in your email address Note: If you are using a legacy system that doesn’t support the Ed25519 algorithm, use: This creates a new ssh key, using the provided email as a label. > Generating public\/private […]<\/p>\n","protected":false},"author":1,"featured_media":807,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[60,33,31],"tags":[61,209,185,210],"_links":{"self":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/836"}],"collection":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=836"}],"version-history":[{"count":5,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/836\/revisions"}],"predecessor-version":[{"id":2805,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/836\/revisions\/2805"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/media\/807"}],"wp:attachment":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}