I'm on windows too, I've never had any issues with msysgit and openssh.

On Sat, Feb 7, 2009 at 4:39 PM, Ibrahim Awwal <[email protected]>wrote:

>
> Well, I'm on Windows, so I'm not sure whether that works but I will
> give it a try. I don't use ssh exactly, I use putty so I'm not sure if
> that makes a difference but I'm assuming it does.
>
> On Feb 6, 6:48 pm, Tekkub <[email protected]> wrote:
> > Do you need pageant?  I just use the same key for ssh that I do for git.
> >  You can also set per-domain options in ~/.ssh/config to use different
> keys
> > for different domains.
> > Yes, you need to use the "your push" url: [email protected]:user/repo.git
> >
> > On Fri, Feb 6, 2009 at 4:44 PM, Ibrahim Awwal <[email protected]
> >wrote:
> >
> >
> >
> > > Well I would like to use Pageant to manage my ssh private/public keys.
> > > I'm going to try to get it to work better with Linux though. So I am
> > > not incorrect in that I need the private URL to push changes, correct?
> >
> > > On Feb 6, 3:15 pm, Tekkub <[email protected]> wrote:
> > > > Unless you have a very good reason to use putty, I would reinstall
> > > msysgit
> > > > and stick with the default openssh.  Putty just complicates the whole
> > > > process from what I've seen, and causes this "bad line length
> character"
> > > for
> > > > some users.
> > > > If you must use putty there is a solution for this, but a quick
> googling
> > > > isn't pulling it up.  I can dig a bit if you want, but I'd recommend
> > > trying
> > > > openssh first.
> >
> > > >     Tekkub
> > > >     Github General Support
> > > >    http://support.github.com/
> > > >     Join us on IRC: #github on freenode.net
> > > >     Discussion group: [email protected]
> >
> > > > On Fri, Feb 6, 2009 at 4:01 PM, Ibrahim Awwal <
> [email protected]
> > > >wrote:
> >
> > > > > Hi guys, I'm trying to learn how to use git. I would have tried it
> > > > > before but I had heard it was slow/buggy on Windows, and while I am
> > > > > fairly proficient with Linux and dual boot, I do prefer Windows
> > > > > overall. But that's beside the point, as msysgit should be working
> for
> > > > > me but isn't. I suspect it has something to do with my public key
> > > > > authentication setup. Here are the details:
> >
> > > > > My repository is here:
> https://github.com/ibrahima/worldwiideweb/tree
> >
> > > > > I was writing some code in C and I had been storing it in a Google
> > > > > Code SVN repository. But then I heard about msysgit so I wanted to
> > > > > move it to github, because I liked the idea of git/github. So I
> > > > > downloaded msysgit, and I already had putty so I created a new
> public/
> > > > > private key pair using Pageant and added the public key to my
> github
> > > > > account. Then, I had github import my SVN repo from Google Code,
> and
> > > > > after several days, it finally finished (which was odd, since there
> > > > > are only 3 source files and a few eclipse project files, and only 8
> > > > > revisions total). Next, I tried to use my github private url and
> msys
> > > > > git bash to clone the newly imported repository, but it failed with
> > > > > the following error:
> > > > > "fatal: protocol error: bad line length character"
> >
> > > > > I do have pageant running with my private key loaded. I am
> suspecting
> > > > > that it's an authentication problem because I can clone from my
> public
> > > > > URL, but unless I'm mistaken I should use the private URL if I want
> to
> > > > > actually commit things? Unless the private URL is only for use with
> > > > > private projects. I also get errors when I try to clone the private
> > > > > URL in linux, so I'm not sure what's wrong. Thanks for the help.
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to