thx for the reply I seem to have gotten past part of my problem after reading this series of posts:
http://www.lostechies.com/blogs/jason_meridth/archive/2009/06/01/git-for-windows-developers-git-series-part-1.aspx I ended up using ssh-keygen to gen the keys. I also think part of my prob was that I hadnt created the repo up on github (!). I thought the push would do that. Had to setup the remote too. So, I created a *public* test repo and have successfully pushed to that. Now, finally moving on to my client's project which I created as a *private* repo, I'm having a problem again. When I try to push there, I now get: FATAL ERROR: Disconnected: No supported authentication methods available Pushing to [email protected]:reefboy/blipitt.git fatal: The remote end hung up unexpectedly I ~think~ it has to do with keys again. But it might be something about github accts. Here are w few details: 1) I have my own acct on github 2) I've been added as a collaborator on the private repo of my client. 3) my public key is stored in my github acct 4) I can push to a public repo tied to my acct 5) I cannot push to the private repo in my client's acct forgive my ignorance, but here are a few questions: * do I only store one key for myself under my acct for access to all repos under any acct on github? * or do I have to store a key under every acct that I want access to (e.g. the client's acct)? * if the answer is no to the first and yes to the second, then it seems that I have to create separate, different keys because when I try to add my existing key to the client's acct I'm told I cant because it's already in use... is this correct? * finally, if I have to create different keys for each acct's repos, isnt there a name conflict waiting to happen if I have multiple private keys on my local machine that I'm ssh'ing in from? thx again if anyone has a direct answer to the error I'm now getting... or answers to the questions. On Nov 3, 12:32 pm, Gaveen Prabhasara <[email protected]> wrote: > Hi, > > I don't think I can tell you how to fix this. But since I have worked with > users on Windows Vista/msysgit setup let me point a couple of things. > > 1. You don't need cygwin to run msysgit. msysgit has a self contained > MSYS environment. So *no* need to install Cygwin. > > 2. PuTTY generated keys are not OpenSSH compatible. If you plan to > use openssh, you'll need to convert the putty generated keys into the > openssh format. This can be done with the putty-keygen (or some other > tool provided with putty) > > So always try to use they ssh-keygen which ships with msysgit. It should > place the keys in correct places. For more > details:http://github.com/guides/using-git-and-github-for-the-windows-for-new... > > I suggest you remove all the existing keys from the system and start > anew. > > 3. If you need to run openssh client, you can get it installed under the > Cygwin environment, i.e. if you wish to use cygwin environment. > > 4. Always try to work in a Git Bash. It can be opened using the right click > menu. If you use the GUI it shouldn't be a problem. > > 5. Check the network/name resolution works correctly. > > 6. You can follow a guide and see how it goes. This came up in a > searchhttp://kylecordes.com/2008/04/30/git-windows-go/ > > Hope these pointers help. > > > > On Wed, Nov 4, 2009 at 1:37 AM, lunaclaire <[email protected]> wrote: > > > I'm trying to get setup to use github and really seem blocked. > > > some details of my setup: > > > I'm on Windows Vista. > > I have cygwin installed which I need for one of the projects I'm > > consulting on. > > I've installed msysgit. > > I use Putty/Pageant/Plink for ssh access to a set of servers and svn > > repos I have. > > I've generated public/private keys using (alternatively) Putty Keygen > > and ssh-keygen (from the Git Bash console) with the same results. > > > And what I'm seeing when I try to do my first git push up to github is > > this: > > > ssh: Could not resolve hostname : Name or service not known > > Pushing to ssh://[email protected]/zaj/blipitt.git > > fatal: The remote end hung up unexpectedly > > > tekkub's suggested that I use openssh instead of the putty set of > > tools, but that seems to conflict w cygwin. During the openssh install > > it warns you not to proceed if you're already using cygwin, so I > > havent switched to openssh (yet). > > > So, I dont know if my problem is: > > > a) that I'm using putty instead of openssh > > b) something in the ssh url I'm using since I get the resolve hostname > > error > > c) something about my keys > > > if it is a), then I wonder if anyone has any experience or suggestions > > about moving to openssh when you're using cygwin? > > > It's hard for me to believe that it's this hard to get this setup on > > windows, so my guess is that I'm doing something stupid. > > > Does anyone else have experience and answers on getting setup with a > > similar environment? > > > Thx in advance. > > > Gaveen Prabhasara > > http://gaveen.owain.orghttp://twitter.com/gaveen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
