Help generating a key on Windows

How frustrating ... I'll be glad to work on sorting this out.

First, during upcoming documentation sprints attention to Windows directions is scheduled.

Second, the most current (and not broken) link for SSH keys is on http://drupal.org/node/1027094 and references http://theillustratednetwork.mvps.org/Ssh/Private-publicKey.html

Sadly, what seems to be GitHub's current directions for TortoiseGit at https://github.com/multitheftauto/multitheftauto/wiki/how-to-use-tortois... leads me to an Internal Server Error.

Finally, it's on my to-do list to write Drupal.org-focused key-gen directions, but I'm not sure when I can get there (Help welcome!)

At the very least I'll look at getting that message that leads to the wrong place updated.

I did find this: http://help.github.com/msysgit-key-setup/, tested the directions and it works. I'll be updating our docs accordingly.

That's an SSH2 format key.

You need to load the key into puttygen and copy paste the text from the "Public key for pasting into OpenSSH authorized_keys2 file:" textarea.

Although I suppose it would be nice if the system used ssh-keygen -i to convert incoming SSH2 pubkeys into the corresponding openssh keys..

"git clone --branch 6.x-1.x salvis@git-testing.drupal.org:project/acl.git acl" should have worked. It's possible that the server was overloaded when you tried or something.

The reason "git clone --branch master http://git-dev.drupal.org/project/acl.git acl" asked for a user name is because git-dev has http authentication to keep the bots out (remember? drupal/drupal) -- It won't work for a git checkout anyway, because it's the drupal.org test instance, not the repo.

Oh, it showed the key cached in registry comment again? That's probabaly what's gumming it up.. Try using putty or plink to connect to git-testing.drupal.org first and accept the fingerprint.

If that was the case, this will need to be documented. I am seeing evidence through searching that this is a common problem when mixing putty with git...

What version of Git are you using? (In Git Bash, type 'git --version')

If you were to join us on Freenode in #drupal-gitsupport, we might be able to sort it out a little faster :)

I could have created better docs if I'd been able to solve this today. As is, this issue will be here for others to help with.

I did create directions at http://drupal.org/node/1066762. Not sure if they'll stay around since the documentation policy says we're supposed to link off-site. Since Drupal.org supplies password auth I can understand that position. Keys are complex enough that I'd wanted to add directions a long time ago but had been dissuaded. Not sure how it will turn out.

Anyway, good luck with the keys.

From git-dev. It'll be open in an hour or so, and it is schedule to stay up for the next couple days.

Yay. I'm going to mark this fixed, then.

The solution is to simple:

1. Start PuTTY
2. Connect to host git.drupal.org
3. Confirm the host's signature/fingerprint
4. Cancel the connection (STRG + C)
5. Done. git should be able to perform all operations regardless of shell now (regular Windows command prompt, msysgit, or cygwin)

Added that info to the howto section on http://drupal.org/node/1027094

Sun, Salvis and Bdragon,

I, too, wish that Sun's 'five-step' fix-it was all that was needed but I am struggling with this as well. I'm on Windows 7 and have an otherwise Happy Camper relationship with TortoiseGit for both GitHub and my own remote repositories. Following the GitHub instructions was so quick and sure-fire that I was up and cooking pronto on that system.

Sadly, I am at a 'how many times will I hit my head on this wall' problem with getting my set-up to work with Drupal's git repo. I followed all the instructions for generating the key pair and got it in my SSH public key section of my DO user account, no sweat. But like salvis, no matter what I try via git-bash, command prompt, TortoiseGit... I get the same showstopper which is the Plink password prompt and the hang up.

I was hopeful that, as BDragon suggested that Puttygen would somehow work into a conversion/update situation. Say, for example, that something would get the DO repo into the known_hosts file in my .ssh subdirectory (which seems to be an important reference for TortoiseGit's putty configuration. Although I may try it, I hestiate to take salvis' approach of reinstalling TortoiseGit to stop using Plink for SSH as this is already working well in other situations. But if that turns out to be the only way, that'll have to do.

I'll keep an eye out for additional insights here and elsewhere and post any advances toward resolving this for myself.

--Sohodojo Jim--

Success!

I killed the TGitCache.exe process via Task Manager and reran the testing command:

git clone mygitdrupalname@git-testing.drupal.org:project/examples.git

which re-prompted for the public key acceptance. This gets the testing-DO repo into my known_hosts file which is good. The clone then inits the empty project directory... again good and expected. But then I am hit with the password prompt.

I then figured I would beat on puttygen a bit (as per Bdragon's suggestion). I then did 'File/Load private key' to import the private key I generated following the basic Drupal Git Windows key/auth instructions. (I had already uploaded my public key into my DO account as per instructions.) I then did a 'Save private key' (a button in the PuTTYgen dialog-window) which converts and saves your SSH-generated key into a 'ppk' file format that TortoiseGit is happy with (when installed with the recommended Plink config rather than SSH alternative).

I then did a typical 'Git clone...' within Windows Explorer in the directory where I wanted my cloned project repo to be.

In the TortoiseGit 'Git clone' dialog, I pasted the username@repo-url portion of the clone command mentioned above (and set the destination directory).

NOW HERE IS THE IMPORTANT PART: I then checked the 'Load Putty Key' checkbox and browsed to the directory and selected the '.ppk' (Plink-friendly) version of my private key, hit 'OK' and WHAM! TortoiseGit opened the 'cloning in process' window and sucked the project right down nothing flat! :-) Yeah, Happy Camper be I!

--Sohodojo Jim--

@Sohodojo Jim: you can use PageAnt to handle and load a set of ppk keys entering only one time their passwords. You should now not check the "load putty key" in GIT dialog.

I'm writing a tutorial on how to set-up Drupal ssh keys with Putty instead of msysgit, you can find it here: http://thepanz.netsons.org/post/drupal-tortoisegit-and-putty-configuration

Hey Panz,

I saw the mention of your article on the mailing list and I greatly appreciate your having taken the time to figure out and document the 'correct' (or at least a substantially better way) to config TortoiseGit for Drupal repo access. In fact, I strongly believe that your article should as quickly as possible find its way into the docs here on the DO site as your method will surely help Windows-based devs to have a cleaner Git-start after the migration.

The experience report I provided is not a right/recommended way as much as it is a 'make-do' for getting back on track after having tried to follow the current instructions that don't work for TortoiseGit folks.

Regardless of whether it is your direct path or a winding road like I unfortunately took, once TortoiseGit is set up correctly, it is a great and efficient means to participate in the post-CVS Drupal Universe.