Just to follow up, the Github help pages have some good tips on setting up 
SSH keys on Windows:


Just skip the part about generating new keys, and the Github specific 
things (like uploading ssh keys in the admin interface).

Usually, these problems are because of:

* SSH is not using the correct key file - you can investigate this by 
looking at the output of "ssh -v git-username@git-server"
* The contents of the key file are corrupted (accidentally added a line 
break when copy/pasting the key, etc) - you can study this by looking at 
the key file in a decent editor (like Notepad++ or something)

On Tuesday, July 10, 2012 4:11:40 AM UTC+2, Les Nightingill wrote:
> The first thing you need to try to diagnose is whether:
> a. the far end is falling back to password access b/c it cannot 
> authenticate the public key you're sending
> b. the pc thinks the local private key requires a password for access
> if you can try an ssh connection using the keys with verbose mode turned 
> on, you might get more insight. It should (ha ha) be pretty much the same 
> command as on the mac.
> sorry, many details missing here, I know, but maybe it gives you a 
> diagnostic start.
> On Monday, July 9, 2012 5:16:48 PM UTC-7, Jackson Beale wrote:
>> I have copied my public and private keys from my mac to my pc. I am using 
>> git bash. The keys work fine on the mac. I have put the keys in 
>> users/owner/.ssh and used the following permissions:
>> chmod 700 ~/.ssh
>> chmod 600 ~/.ssh/*
>> chmod 644 ~/.ssh/known_hosts
>> When I try and clone the remote repo, I am asked for a password. Any ideas?

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to