When working with a GitHub repository, you'll often need to identify yourself to GitHub using your username and password. Using the same technique to instead link the symlink directory as suggested by tripleee, I had issues until I.
With GitBash I found I had to copy my ~/. Ssh/id_rsa file to Program Files\Git\. Ssh\id_rsa - which was a little confusing, but now IntelliJ and Windows cmd can push to git repositories that use key authentication. I just installed git-for-windows, I am running it from cmd. I needed to put the files id_rsa and id_rsa. Pub into c:\program files (x86)\Git\. Ssh dir was already present.
Damon: It should be id_rsa without the extension. Using the built-in SSH client shipped with Git for windows, you need to setup the HOME environment variable so that the Git SSH client can find the key. For example, on a Windows Vista installation, this would be done by issuing setx HOME c:\Users\admin\ on the command line. Made my day and fixed the issue with Git provided that your private key is not password protected.
If you want to use ssh-agent, then you can probably run ssh-agent cmd.
Почему лучше использовать SSH ключи для авторизации
Exe (although I've never done that) and the ssh-add as usual. Note that all Git/SSH tools are supposed to be run from a cmd. Exe in order not to blink a window. If this does not work correctly, using plink can probably be achieved by tweaking GIT_SSH. Refer to all the svn+ssh tutorials, this is basically the same plumbing you need to setup. This is what I was looking for since I'm trying to use the Windows command prompt, not git bash.
Important is as well to have no blanks between HOME = and c:\. Oct's solution did the trick for me. Worth noting - if you have spaces in your home (if you are using win XP/server 2003 you will), then you should prefix the path with a single quote. Bizarrely - if you end it with a quote that will be in the variable.
The setx HOME c:\Users\admin` command doesn't seems to be working in Git Bash. You have to use cmd` instead. Set the Path to your Putty Key in the corresponding Input Box.
Информационный портал по безопасности
Additionally if you need to convert your private key into '. A much easier solution is to set everything up working properly in git (using openSSH), and then tell TortoiseGit to use the ssh. See That way, you only need to fix this once. None of the answers above worked for me. Here was what worked for me in the end. It is actually fairly simple, if you know what to type. That's the bit on your own computer done. Now ssh into the destination server, then do mkdir -p ~/.
Разное Использование нескольких SSH ключей в Git
From git bash, do the following to test: ssh someuser@someserver. If it lists the files in your home directory on the git server, then you're done! In git bash, type 'cat ~/. Don't create keys without passphrases. It's like putting your password in a text file, except that everyone knows the default location for private keys. You're answering the wrong question. The Q is how to point to an existing private key. GregB, I look at it like this: any server for which I create a password-less key is as secure as my laptop, it's an extension of the security perimeter of my laptop.
Actually, not even, since my home directory is encrypted;-) So, it's as secure as the encrypted home partition on my laptop, which is 'good enough' for securing access to github, in my opinion. (which may vary from your opinion of course! GregB Don't fall down into paranoia! Sure, that using password-protected keys is much more secure, than using password-less, but claiming that password-less key is as easy to break as storing passwords in a text file is an obvious false. I've seen many guides, that encourage users to use password-protected keys, but I have never seen any claiming, that using them without passwords is not secure at all.
Plus: some systems doesn't support solutions for remembering key's password, entered by users, and asks for it, each time key is used. Which makes using SSH keys pointless in this situation. For the sake of the conversation, which has deviated from the original question, SSH keys are certainly more cryptographically secure than passwords, but that security is put at risk by not encrypting your SSH keys. My personal approach is to unlock my keys at the beginning of the day using an SSH agent, which then keeps the decrypted keys in memory so that I don't need to re-enter the password throughout the day.
As @Hugh Perkins comments, and I'm paraphrasing, you all know your security requirements better than I/we do:). If you're using msysgit with the OpenSSH tools, you need to either create ~/. Ssh/id_rsa, or create a git config in ~/. Ssh/config which points to your key. Here's an example of a Git config for bitbucket that will use the correct username, and a key other than the default key (in case you maintain one key for SSH connections, and another for git accounts). Once in git bash, you can run two commands to add your key to your current session's ssh-agent to avoid having to repeatedly type the key's password.
I did this but for github. This has the advantage of working for all users logged into the system (they each get separate. Note that %HOMEPATH% does not contain the drive letter, so if your source is not on C: you need to prepend C: to %HOME%.
Related Inchoo Services
Your private key needs to be added to the SSH agent on your workstation. I stated above that I'm using Git for Windows and am using ssh. Exe (packaged w/ git) in lieu of putty. There must be some standard practice for adding a private key, I just can't seem to find out how. While switching software may indeed allow me to log in, there has to be a way to do it with the standard Git setup, no?
How do I tell Git for Windows where to find my private RSA key
Sorry i dont work on windows, only linux. But the key does have to be in your SSH agent. Exe or something along those lines? Yeah, setup was cake on the linux side. But I've got to have it working on Windows too unfortunately. There are several ssh-related executable files in the git/bin folder on the Windows box (ssh, ssh-add, ssh-agent, ssh-keygen & ssh-keyscan), but I don't know how to make any of them do anything.
Создание публичного SSH-ключа
They just blink a cmd window open and close right away. Pageant does indeed solve the problem for me -- I have a shortcut in my Start Menu's Startup folder (C:\Users\owen. Blacker\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup) pointing to "C:\Program Files (x86)\PuTTY\pageant. Blacker\Documents\SSH\OwenBlackerPersonal. Blacker\Documents\SSH\OwenBlackerWork. You definitely should write this comment as a full-size answer!
This is the only solution here, that actually helped me and solved my problem! Pity, that I can give you only +1! But placeing in my private ssh keys in public folder i didn't was good idea so i started to look where are is the knownhost. This was the simplest solution on my Win7 machine. Like you, I searched for known_hosts.
3 Git на сервере - Создание открытого SSH-ключа
Sure enough, it was in C:\Users\Dave\AppData\Local\VirtualStore\Program Files (x86)\Git\. By placing my key file (id_rsa) in that directory, ssh was able to find it without complaint.
I did a little reading - this is how Windows handles (legacy) software attempting to write to forbidden areas (such as "C:\Program Files\"), so Git's ssh is completely unaware that it is writing to the VirtualStore directory, Windows is handling that transparently. At least these files belong to a user!
With this: Host example. Then I was could use key from C:\Users\\. I'd add one more detail, if you are using git for windows together with openSSH for windows. Git is still using it's own ssh. Plus if you plan using ssh-keyscan host. Com > known_hosts from openSSH be careful because piping output from stdout of keyscan(on windows) changes encoding to UCS-2 but openSSH can read only utf-8! So make sure to change the known_hosts file encoding.
This helped, but for anyone who's using an id_dsa key, you'll also need to add "PubkeyAcceptedKeyTypes ssh-dss" under your host. When mixing GitHub for Windows and Git GUI for windows, you might run into issues where Git GUI keeps prompting you for a username and password. The cure for this is to change the remote url from: (which is what GitHub for Windows creates) to git protocol.
It is natural and easy to clone a repo with github for windows GUI, but when use git cui outside of git shell failed. I wonder how the git command in the git shell works with url. Following the link you provided I was able to get my Jenkins setup. I needed to set the HOME environment variable to the Git program path which held the.
How can I change the directory that ssh-keygen outputs to
Ssh directory I created my SSH key in. I had similar issues and none of the answers here solved the problem. Turns out, my key pair were originally generated with an empty passphrase. Once I created a new keypair and uploaded the public key to github, things started working again.