SSH Key - Still asking for password and passphrase

Question

I've been somewhat 'putting up' with Github always asking for my username and password when I clone a repository. I want to bypass this step because it is an annoyance within my workflow.

I tried setting up an SSH key (which I successfully did) using this guide. https://help.github.com/articles/generating-ssh-keys and I was successful.

My problem is that I am still asked for my github password and passphrase when cloning a repository (using SSH). My understanding was that after I set up this SSH key, I would no longer have to do that.

I am a little unsure what to ask, so I will just state my goal.

I want to be able to clone repositories without having to put in my Github information all the time.

What am I missing with my SSH key? If anyone can provide some guidance or resources I would appreciate it, because I've always felt a little lost when it came to SSH authentication in GitHub.

From my knowledge, this is a command that tests if things are working properly, here are the output from my console:

~ $ ssh -T [email protected]
Saving password to keychain failed
Enter passphrase for key '/Users/MYNAME/.ssh/id_rsa':
Hi MYNAME! You've successfully authenticated, but GitHub does not provide shell access.

When I input my password, should that fail first? Then, when I enter my passphrase, it passes.

Inform

In which OS are you? A modern Linux Desktop would propose to store your passphrase in a keyring manager. Same in Mac OS X. In Windows you can use pageant, which is part of putty. In all these the goal is the same: you enter the passphrase only once after you start your PC, the key manager agents will pass it to ssh in subsequent uses until you reboot. – Psychodynamics

Duplicate of Git push requires username and password – Palm

I'm a little late to the party here, but on the little clone tab/button in github there is a link that says "Use SSH". You want to do that. It changes your clone link to something like "git@github:username/project.git". If you added an SSH key to github and have it running on ssh-agent locally, then you should be able to push without entering a username or password. – Bronco

You can also consider this cross-site Q/A or Git keeps prompting me for a password (potential duplicate) – Tiliaceous

This works for me: dev.to/solrevdev/windows-does-not-remember-git-password-lmh – Sharper

Answer 1

If you work with HTTPs urls, it'll always ask for your username / password. This could be solved using @Manavalan Gajapathy's comment (copying here):

See this github doc to convert remote's URL from https to ssh. To check if remote's URL is ssh or https, use git remote -v. To switch from https to ssh:

git remote set-url origin [email protected]:USERNAME/REPOSITORY.git

If you're correctly using SSH when cloning / setting remotes: make sure you have a ssh-agent to remember your password (see this answer by @Komu). That way, you'll only enter your passphrase once by terminal session.

If it is still too annoying, then simply set a ssh-key without passphrase.

Tyranny

thanks for the response. I've always just used HTTPs. I am trying to achieve SSH authentication and thought I set it up. Is the ssh-agent something outside of git I need to install? Thanks – Inform

Codey, it depends, sometime its there by default, sometime not. See this answer too: stackoverflow.com/questions/18404272/… – Tyranny

If I forget my paraphrase, then how can I get ssh-agent to let me know what it was ? – Mottle

@Mottle you cannot, otherwise passwords wouldn't be secure... Just regenerate a new one. – Tyranny

I just want to note that passphrases are used to encrypt your private key, so if you don't use a passphrase, then your private key will be unencrypted on your machine. It's like leaving a password in a text file laying around on your computer. – Palm

Funny, my HTTPS repos never ask for passwords and my SSH repos always do. – Culture

See this github doc to convert remote's URL from https to ssh. To check if remote's URL is ssh or https, use git remote -v. To switch from https to ssh: git remote set-url origin [email protected]:USERNAME/REPOSITORY.git – Old

Downvoted because the "what" should include a "how". – Maniac

Thanks I searched for so many answers and yours work. After setting the ssh key the only missing step from me is git remote set-url origin [email protected]:USERNAME/REPOSITORY.git . – Marlysmarmaduke

Answer 2

Add Identity without Keychain

There may be times in which you don't want the passphrase stored in the keychain, but don't want to have to enter the passphrase over and over again.

You can do that like this:

ssh-add ~/.ssh/id_rsa 

This will ask you for the passphrase, enter it and it will not ask again until you restart.

Add Identity Using Keychain

As @dennis points out in the comments, to persist the passphrase through restarts by storing it in your keychain, you can use the --apple-use-keychain option (-k for Ubuntu) when adding the identity like this:

ssh-add --apple-use-keychain ~/.ssh/id_rsa

Once again, this will ask you for the passphrase, enter it and this time it will never ask again for this identity.

Ruthieruthless

lower case -k for me... (Linux Mint / Ubuntu 14.04 base) but yes! finally sorted this... – Unplumbed

I was having a bunch of random problems with ssh. I typed in ssh-add to see if the command was even installed on my computer, and it somehow solved everything immediately. – Provocative

just running the command "ssh-add" and enter the password once, command line will not prompt you for the password again. – Sciomancy

I tried lots of different things and this is the one that worked. Thanks @Komu! – Threephase

You don't need any arguments; just running ssh-add will automatically add ~/.ssh/id_rsa (among other files). And there's no reason to send the output to /dev/null; much better to see the report of what it did. – Sorry

Any idea why I get "Could not open a connection to your authentication agent."? – Wolverhampton

ssh-add still isn't saving it across restarts for me. Even with -k. My keys work fine for putty, the problem seems to be git bash – Unawares

If you would simply like to be asked less often, you can use the -t flag: ssh-add -t 3600 ~/.ssh/id_rsa -- this will ask you for the passphrase, enter it and it will not ask again for 1 hour (3600 seconds). – Refund

Once I added ssh public key to git account then following command ssh-add -A fixed the issue with passphrase prompt. – Lyallpur

ssh-add -K ~/.ssh/id_rsa -K is unknown.. same goes for -A... Ubuntu 18 – Donniedonnish

In Ubuntu the -k flag is for "Load only keys and not certificates". To make keys persist create the file ~/.ssh/config and add a line for the corresponding key IdentityFile ~/.ssh/id_rsa. This can be expanded to configure specific hosts, ports, users etc. search "ssh config file" to dive deeper. – Zeuxis

see also another answer containing more details about config file – Eucken

Worked fine in macOS Mojave – Hyperaemia

If you get an error saying "Could not open a connection to your authentication agent.", try eval `ssh-agent` followed by ssh-add – Disgruntle

@dimmech: IdentityFile says which key to use for that host. The -k intended is to store the keys passphrase. These are not the same. – Mcdermott

"k" should always lower case only as per official document. ssh.com/ssh/add – Bohun

Windows users should not rely on ~ being a suitable identifier, see superuser.com/a/1655228/356039 – Hat

@Wolverhampton ssh-agent needs to be running. See this for more info: wiki.archlinux.org/title/SSH_keys#SSH_agents – Deposition

-K is deprecated – Cyna

For Debian Xfce going into the /etc/ssh/ssh_config and uncommenting the IdentityFile associated with the key (for me it was IdentityFile ~/.ssh/id_ed25519) then I also used ssh-sdd ~/.ssh/id_ed25519 in the user accounts affected. – Upstretched

Answer 3

On Mac OSX you can add your private key to the keychain using the command:

ssh-add -K /path/to/private_key

If your private key is stored at ~/.ssh and is named id_rsa:

ssh-add -K ~/.ssh/id_rsa

You will then be prompted for your password, which will be stored in your keychain.

Edit - Handle restart

In order to not have to fill in your password even after a restart add the following to your ssh configuration file (commonly located at ~/.ssh/config)

Host *
  UseKeychain yes
  AddKeysToAgent yes
  IdentityFile ~/.ssh/id_rsa

Hyde

In my case, it's still prompting for the passphrase after restart (macOS Sierrra 10.12.2). Any ideas on how to solve this? – Baa

Nevermind, I've just found the issue. It's a bug (feature?) from Mac OS X 10.12 in which the ssh-agent does not automatically load passphrases on the keychain during startup. github.com/lionheart/openradar-mirror/issues/15361 – Baa

@Groot, BTW, adding "Host * UseKeychain yes" to "~/.ssh/config", as suggested in other answers, fixes the issue. – Baa

This should be the accepted answer. Specially the config file in ~/.ssh – Renayrenckens

I kept getting prompts to "Enter passphrase for key .ssh/id_rsa:" - ssh-add -K ~/.ssh/id_rsa resolved this – Humberto

After adding a config file with your answer, I get this error on macOS 14 Sonoma: .ssh/config: line 2: Bad configuration option: usekeychain and .ssh/config: terminating, 1 bad configuration options – Fibro

Answer 4

I tried all the answers here and none of these answers worked! My password would not persist between sessions/restarts of my Mac.

What I found out from reading this OpenRadar and this Twitter discussion was that Apple purposely changed the behaviour for ssh-agent in macOS 10.12 Sierra to no longer automatically load the previous SSH keys. In order to maintain the same behaviour as El Capitan I did the following:

1. ssh-add --apple-use-keychain ~/.ssh/id_rsa

• Note: change the path to where your id_rsa key is located. Also, --apple-use-keychain was previously -K.

2. ssh-add --apple-load-keychain

• Note: --apple-load-keychain was previously -A.

3. Create (or edit if it exists) the following ~/.ssh/config file:

    Host *
      UseKeychain yes
      AddKeysToAgent yes
      IdentityFile ~/.ssh/id_rsa
   

And now my password is remembered between restarts of my Mac!

Ramie

This might be something useful to add to either the github or osx documentation pages. Had the hardest time figuring out why my Mac running 10.11 and my other running 10.12 where behaving differently. – Salvatore

Happened to me after an OSX upgrade, thanks (I think ssh-add -A is not needed if you have only one key at ~/.ssh/id_rsa) – Stjohn

I just upgraded to macOS 10.12 and this was super useful. Thanks! – Tate

As of October 2017, this answer is exactly what you're looking for if you are using macOS 10.12 or higher. – Walloping

Thanks @Walloping for confirming it works in macOS 10.13 High Sierra! – Ramie

Still worked for me on latest Sierra (10.12.6) Thanks a bunch!! – Humberto

And this is now on the github docs: help.github.com/articles/… – Leoine

Answer 5

You can remove passphrase for the key

$ ssh-keygen -p [-P old_passphrase] [-N new_passphrase] [-f keyfile]

or you can run

$ ssh-keygen -p

you get a prompt for keyfile. By default it ~/.ssh/id_rsa so press enter

You'll be prompted for current pass phrase enter it.

Then there will be a prompt for new pass phrase, press enter

Contentment

This should be higher than a lot of the nearly identical answers for adding the passphrase to the keychain. I had to give my public key to an administrator, and included a passphrase which became annoying to type every time. This is a clean solution when you don't have much control over your machine (-K, -k, -A did not work for me). – Gigantic

This is the only thing that worked for me across restarts, all the ssh-add -K, -k, etc. commands didn't do a thing for me. – Unawares

It works perfectly for me too, I used the first approach ssh-keygen -p -P MyOldPassPhrase -N "" -f ~/.ssh/mykeyfile. Thanks! – Graeme

This is the answer. – Angelitaangell

This is the best answer. Worked perfectly. Bear in mind to not add any password, just press enter in each step and it will do the trick. – Temperance

Answer 6

TL;DR
You need to use an ssh agent. To do that, open terminal & before pushing to git, execute

ssh-add

enter your passphrase when prompted.

Check out the original StackExchange answer here

Alimentary

This works, but what happens is that you have to repeat this command each time you boot your computer. – Gossett

@WilliamGrand this hasn't been the case for me though but if you're saying then, of course, I believe you :]. I'll see if I can find anything & I'll update the answer accordingly. – Alimentary

Answer 7

Make sure you are using ssh for your repository also

mahtab@mahtab-Lenovo-G50-70:~/my-projects/jenkins-cje-2017$ git remote -v origin [email protected]:eMahtab/jenkins-cje-2017.git (fetch) origin [email protected]:eMahtab/jenkins-cje-2017.git (push)

Don't use https, if your remote is using https then it will keep asking for password, even If you have added the public key to Github and added private key to ssh-agent. Below will always ask for password

mahtab@mahtab-Lenovo-G50-70:~/my-projects/jenkins-cje-2017$ git remote -v origin https://github.com/eMahtab/jenkins-cje-2017.git (fetch) origin https://github.com/eMahtab/jenkins-cje-2017.git (push)

Chambers

Yes differentiating between the two remote URL types was helpful for me. This helped me in terms of git pull and git push. I switched my url from HTTPS type to SSH type, and it worked--git pull stopped asking for password. – Irksome

Switching can be done with this command: git remote set-url origin [email protected]:USERNAME/REPOSITORY.git – Dimorph

Answer 8

Just run the following command:

ssh-add -K

It will never ask you to enter the password again.

Rosaliarosalie

This works great, but I was a little concerned about running a random command. However, if you check the docs ssh-add just "adds private key identities to the authentication agent", and the -K option simply makes it so "When adding identities, each passphrase will also be stored in the user's keychain." – Pregnant

Actually, it only fixed it until I restarted :( – Pregnant

in the bash shell for Windows, the "-k" flag has to be lowercase. Just FYI – Uniat

The option -K is not available on prior versions of ssh-add. This is why it is not working for many. The option -k (lower case) IS NOT the same and you will have to re-type your passphrase next time you open a session. – Graeme

Answer 9

I had to execute:

eval `ssh-agent -s`
ssh-add

Note: You will have to do this again after every restart. If you want to avoid it, then enter it in your ".bashrc" file which is in C:\Users\<<USERNAME>>\.bashrc on windows. It is probably hidden, so make sure that you can see hidden files.

Solution found here.

Clinkstone

Answer 10

This page on github has the answer you need. You have to switch to ssh authentication from https.

Check how it is authenticating as follows.

$ git remote -v
> origin  https://github.com/USERNAME/REPOSITORY.git (fetch)
> origin  https://github.com/USERNAME/REPOSITORY.git (push)

Change your remote's URL from HTTPS to SSH with the git remote set-url command.

$ git remote set-url origin [email protected]:USERNAME/REPOSITORY.git

Test it again with

$ git remote -v
# Verify new remote URL
> origin  [email protected]:USERNAME/REPOSITORY.git (fetch)
> origin  [email protected]:USERNAME/REPOSITORY.git (push)

That's all. It will work now.

Taillight

This answer works if you the remote repo url is changed from https to ssh. Thanks. – Selfpropelled

Answer 11

If you're using windows, this worked for me:

eval `ssh-agent -s`
ssh-add ~/.ssh/*_rsa

It'll ask for passphrase in the second command, and that's it.

Add these lines to your bash profile, $HOME/.bash_profile or $HOME/.bashrc.

Symptomatic

When you logout and relog you have to re-enter the password each time. – Backslide

Answer 12

Use ssh-add command to add your public key to the ssh-agent.

ssh-add

Make sure the ssh public key e.g. ~/.ssh/id_rsa.pub is what you have in your repo settings.

Make sure you can actually ssh into the server e.g. For Bitbucket:

ssh -T [email protected]

Update the url to move from https to ssh. You can check which you use by checking the output of:

git remote -v

If you see a https:// in the urls, then you are still using https. To update it: Take the url and just replace https:// with ssh:// e.g. Change:

https://[email protected]/../..

To:

ssh://[email protected]/../..

Referenced: https://docs.github.com/en/github/using-git/changing-a-remotes-url#switching-remote-urls-from-https-to-ssh

Persis

Answer 13

Try ssh-agent as it is explained there : https://help.github.com/articles/working-with-ssh-key-passphrases

Assentor

Answer 14

This is what worked for me:

git config --global core.sshCommand "'C:\Windows\System32\OpenSSH\ssh.exe'"

Ringnecked

Thanks, didn't think about that, I use windows ssh with the config to access my servers via ssh, and it works with keys and stores passphrase seamlessly, never thought I can do that for git too. Thanks! – Umbilical

Answer 15

For Mac OSX Sierra, I found that the fixes suggested in the github issue for Open Radar fixed my problem. Seems like Sierra changed the default behavior (I started having this problem after upgrading).

This one I found especially useful: https://github.com/lionheart/openradar-mirror/issues/15361#issuecomment-249059061

ssh-add -A 

This resulted in my identity being added to the agent, after I ran

ssh-add -K {/path/to/key}

To summarize, in OSX.12:

ssh-add -K {/path/to/key}
ssh-add -A 

should result in:

Identity added: {/path/to/file} ({/path/to/file})

EDIT: I noticed the next time I did a full reboot (aka the agent stopped and restarted) this no longer worked. The more complete solution is what @ChrisJF mentioned above: creating a ~/.ssh/config file. Here's the output of mine:

$ cat ~/.ssh/config
Host *
  UseKeychain yes
  AddKeysToAgent yes
  IdentityFile ~/.ssh/id_rsa

You can add as many IdentityFile entries as you need, but this is the default setup. This is the "trending" answer on the openradar link above, ATM, as well.

Braden

The edited one solved my issue. MacOS Mojave 10.14.3 – Contrivance

Answer 16

Worked in LinuxMint/Ubuntu

Do the following steps

Step 1:

Goto file => /.ssh/config

Save the below lines into the file

Host bitbucket.org
    HostName bitbucket.org
    User git
    IdentityFile /home/apple/myssh-privatekey
    AddKeysToAgent yes

Don't forget to add this line AddKeysToAgent yes

Step 2:

Open the terminal and add the keyset to the ssh-add

$ ssh-add -k /home/apple/myssh-privatekey

provide the passphrase.

Tiruchirapalli

Answer 17

I recently upgraded to macOS Mojave, and installed some tools via homebrew, which seemed to swap Apple's version of ssh-add for the different one. My default version of ssh-add did not have the -K option. This led to the following error:

# ssh-add: illegal option -- K

You can see which version of ssh-add you have by running which ssh-add.

(Mine was stored in /usr/local/bin/ssh-add)

To fix this, I had to point the key to Apple's version:

/usr/bin/ssh-add -K ~/.ssh/id_rsa

Git/GitHub worked perfectly afterward. For more information, see: Error: ssh-add: illegal option -- K

Iddo

Had the same problem on my iMac with High Sierra 10.13.6 - this worked for me. Thanks! – Shortbread

Mine had been working fine & randomly started asking for passphrases again - might've been after a recent update. This fixed it! Thanks – Upend

Answer 18

This answer is primarily for windows users and also equally relevant if you're having trouble cloning with tfs, github or gitlab on any other OS.

The default authentication mode when using SSH is the private key. Whenever that fails for some reason, the ssh-agent falls back to username and password based authentication.

There are several reasons why the default key based authentication might have failed. Following are the most common cases :

a) The ssh-agent cannot find the default private key file which is id_rsa, and no other key path is specified explicitly.

b) The public key stored in the server is incorrect.

c) The path you're trying to clone is incorrect.

In any case, to troubleshoot the issue, first of all execute the git clone command with verbose logging with the command :

GIT_TRACE=1 GIT_SSH_COMMAND="ssh -vvv" git clone ssh://pathToYourRepo

You can go through each step in the log to get an intuition of what the issue might be.

---

Troubleshooting in case of (a)

• Make sure you have the default key name id_rsa in the .ssh directory. You might have specified some different keyname when generating the key with ssh-keygen command or maybe there isn't any key at all).

• In case you want to specify a different key for authentication, use the following command :

   ssh-agent bash -c 'ssh-add ~/.ssh/anotherKey; git clone ssh://pathToYourRepo'
  

---

Troubleshooting in case of (b)

• Make sure there aren't extra white spaces when storing the public key in the server.

---

Troubleshooting in case of (c)

• Make sure you aren't trying to clone with the https version of the repository path.

Caitiff

..."Make sure you aren't trying to clone with the https version of the repository path"... OH... thank you!!! – Secure

Answer 19

If you used for your GIT the password authentication before, but now are using SSH authentication, you need to switch remote URLs from HTTPS to SSH:

git remote set-url origin [email protected]:USERNAME/REPOSITORY.git

Cassiterite

Answer 20

I already had set a passphrase but for some reason it wouldn't recognize it anymore. So I just added the identity file to my keychain again using ssh-add -K and it stopped asking for my password.

Giuseppe

this only loads keys and not certificates – Stoeber

Answer 21

Adding to the above answers. Had to do one more step on Windows for git to be able to use ssh-agent.

Had to run the following command in powershell to update the environment variable:

PS> [Environment]::SetEnvironmentVariable("GIT_SSH", "$((Get-Command ssh).Source)", [System.EnvironmentVariableTarget]::User)

Restart VSCode, Powershell or whatever terminal you are using to activate the env variable.

Complete instructions can be found [here] (https://snowdrift.tech/cli/ssh/git/tutorials/2019/01/31/using-ssh-agent-git-windows.html).

Fairley

Answer 22

Problem seems to be because you're cloning from HTTPS and not SSH. I tried all the other solutions here but was still experiencing problems. This did it for me.

Using the osxkeychain helper like so:

1. Find out if you have it installed.

   git credential-osxkeychain

2. If it's not installed, you'll be prompted to download it as part of Xcode Command Line Tools.

3. If it is installed, tell Git to use osxkeychain helper using the global credential.helper config:

   git config --global credential.helper osxkeychain

The next time you clone an HTTPS url, you'll be prompted for the username/password, and to grant access to the OSX keychain. After you do this the first time, it should be saved in your keychain and you won't have to type it in again.

Abbieabbot

Answer 23

Generally, here are the steps to allow you make a remote connection to your server using ssh without password:

• Create a pair of rsa private and public key

  $ ssh-keygen -t rsa -b 4096 -C "your comments"
  

• Copy your public key and login to your remote server

• Add your public key to .ssh/authorized_keys

• If you have multiple ssh keys in your computer you might to add your key using ssh-add

  $ ssh-add /path/to/private/key

• Then try ssh to your server

  $ ssh username@your_ip_address

Source: http://diary-of-programmer.blogspot.com/2018/08/tips-how-to-ssh-to-your-digitalocean.html

Assizes

Answer 24

SSH Key - Still asking for password and passphrase

If on Windows and using PuTTY as the SSH key generator, this quick & easy solution turned out to be the only working solution for me using a plain windows command line:

1. Your PuTTY installation should come with several executable, among others, pageant.exe and plink.exe
2. When generating a SSH key with PuttyGen, the key is stored with the .ppk extension
3. Run "full\path\to\your\pageant.exe" "full\path\to\your\key.ppk" (must be quoted). This will execute the pageant service and register your key (after entering the password).
4. Set environment variable GIT_SSH=full\path\to\plink.exe (must not be quoted). This will redirect git ssh-communication-related commands to plink that will use the pageantservice for authentication without asking for the password again.

Done!

Note1: This documentation warns about some peculiarities when working with the GIT_SHH environment variable settings. I can push, pull, fetch with any number of additional parameters to the command and everything works just fine for me (without any need to write an extra script as suggested therein).

Note2: Path to PuTTY instalation is usually in PATH so may be omitted. Anyway, I prefer specifying the full paths.

Automation:

The following batch file can be run before using git from command line. It illustrates the usage of the settings:

git-init.bat
   @ECHO OFF
   :: Use start since the call is blocking
   START "%ProgramFiles%\PuTTY\pageant.exe" "%HOMEDRIVE%%HOMEPATH%\.ssh\id_ed00000.ppk"
   SET GIT_SSH=%ProgramFiles%\PuTTY\plink.exe

Anyway, I have the GIT_SSH variable set in SystemPropertiesAdvanced.exe > Environment variables and the pageant.exe added as the Run registry key (*).

(*) Steps to add a Run registry key>

1. run regedit.exe
2. Navigate to HKEY_CURRENT_USER > Software > Microsoft > Windows > CurrentVersion > Run
3. Do (menu) Edit > New > String Value
4. Enter an arbitrary (but unique) name
5. Do (menu) Edit > Modify... (or double-click)
6. Enter the quotes-enclosed path to pageant.exe and public key, e.g., "C:\Program Files\PuTTY\pageant.exe" "C:\Users\username\.ssh\id_ed00000.ppk" (notice that %ProgramFiles% etc. variables do not work in here unless choosing Expandable string value in place of the String value in step 3.).

Libation

Answer 25

If you are using ssh url for git, when prompted for password for ssh put the username as "git" and the password as your system's login password

Ecumenicalism

Changing repository remote URL type from HTTPS to SSH solved my issue. Thanks @MichaelR, your article was really helpful, though I haven't read anything from it :D – Derisive

Answer 26

Use ssh remote url provided by Github not https.

Cubiculum

The OP clearly said he's using SSH instead of HTTPS. – Chockfull

Answer 27

I'd like to add an answer for those who may still need to enter the password because they have set IdentitiesOnly as yes. This may cause by multiple keys and the identity file, being keys for git or server.

After I have generated the key and copied it to the server:

ssh-keygen
ssh-copy-id -i ~/.ssh/12gpu_server.pub [email protected]

I found it didn't work.

Then I went to check the ~/.ssh/config file, I saw this at the bottom:

Host *
IdentitiesOnly yes

Then I add this above:

Host 12gpu
HostName 192.168.20.160
User lerner
IdentityFile ~/.ssh/12gpu_server

I can just log in by entering ssh 12gpu.

Then you can add multiple ssh keys using your favorite names, and you only need to add the settings like the above four lines to the config file.

Host is the name you'd like to enter when you connect to the server later; the HostName is the server's ip or domain like github.com; User is the user name you log in the server like the user name or git for github or gitlab; and the IdentityFile is the file where you store the key you have generated.

Paperhanger

Answer 28

If you are using Windows and GIT without third party tools and your key is not secured by a password / passphrase use this:

1. Environment Variable HOME must be set to your user profile (e.g. C:\Users\Laptop)
2. Go to C:\Users\Laptop\.ssh\ folder and edit "config" file (or create the file!) Example: C:\Users\Laptop.ssh\config (note: there is no . at the end!)

3. Add your git-server host to the "config" file like so:

   #Example host entry
   Host myhostname.com
       HostName myhostname.com
       User git
       IdentityFile c:/users/laptop/.ssh/id_rsa.pub
       PasswordAuthentication no
       Port 422
   

4. Save the file and clone the repository like this:

   git clone ssh://myhostname.com/git-server/repos/picalc.git

You can use additional configuration parameters for the "config" file host entry. These can be found in your local git installation folder, e.g. "C:\Program Files\Git\etc\ssh\ssh_config". Excerpt:

# Host *
#   ForwardAgent no
#   ForwardX11 no
#   RhostsRSAAuthentication no
#   RSAAuthentication yes
#   PasswordAuthentication yes
#   HostbasedAuthentication no
#   GSSAPIAuthentication no
#   GSSAPIDelegateCredentials no
#   BatchMode no
#   CheckHostIP yes
#   AddressFamily any
#   ConnectTimeout 0
#   StrictHostKeyChecking ask
#   IdentityFile ~/.ssh/identity
#   IdentityFile ~/.ssh/id_rsa
#   IdentityFile ~/.ssh/id_dsa
#   IdentityFile ~/.ssh/id_ecdsa
#   IdentityFile ~/.ssh/id_ed25519
#   Port 22
#   Protocol 2
#   Cipher 3des
#   Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
#   MACs hmac-md5,hmac-sha1,[email protected],hmac-ripemd160
#   EscapeChar ~
#   Tunnel no
#   TunnelDevice any:any
#   PermitLocalCommand no
#   VisualHostKey no
#   ProxyCommand ssh -q -W %h:%p gateway.example.com
#   RekeyLimit 1G 1h

Scaleboard

Answer 29

Same problem to me and the solution was:

See this github doc to convert remote's URL from https to ssh. To check if remote's URL is ssh or https, use git remote -v. To switch from https to ssh: git remote set-url origin [email protected]:USERNAME/REPOSITORY.git @jeeYem

Grout

Answer 30

Mobaxterme had a UI interface for it

setting > configuration > SSH > SSH Agent > [check] Use internal SSH agent "moboAgent" > add [your id_rsa and restart mobaxterme to set changes]

Sleeper

Answer 31

As explained in Cloning a Git repo from VSTS over SSH asks a password! Unexpected

The problem may be because of public key authentication failing, so it then asks for mycompany account's password.

This would not happen if the public key authentication succeeded.

So you might check id_rsa.pub and even create a new one.

Pankey

Answer 32

The way that worked for me (windows 10)

1. open git-gui from applications
2. help
3. show ssh-keys
4. generate ssh-key
5. copy ssh key to git provider

This way we guarantee that git client is pointing to the valid ssh

Brubaker

Answer 33

I creation ssh key, added it to ssh agent, added it to my github profile. All according to github official instructions. BUT connection didn't establish. I fixed it by calling ssh -T [email protected] in terminal. Then I got message "Permanently added 'github.com' (ED25519) to the list of known hosts". And all started to work!

Apyretic

Answer 34

I had the same issue and this was my solution.

First check the OpenSSH version in your computer.

ssh -V

If it is greater than 8.8, Then check whether your keys's type is RSA.

ssh-keygen -l -f ${PATH_TO_KEY}

If it says, RSA like below you are in trouble.

3072 SHA256:SSH_KEY_FINGERPRINT YOUR_NAME@YOUR_HOST (RSA)

Because the greater OpenSSH versions than 8.8 do not accept the RSA keys. So generate and use Ed25519 keys as below.

ssh-keygen -t ed25519

Rheinlander