From: Reini Urban <rurban@x-ray.at>
To: cygwin@cygwin.com
Subject: Re: ssh-keygen command not doing anything OR github problem
Date: Fri, 04 Feb 2011 06:33:00 -0000 [thread overview]
Message-ID: <AANLkTin8YjDU+0bWeDatv-vga4rD9OmC24GunZ9Qj2V3@mail.gmail.com> (raw)
In-Reply-To: <30829947.post@talk.nabble.com>
2011/2/2 mearrex:
> In my cygwin installation, I cannot seem to use github.com. However, here are
> the problems I am seeing.
>
> When I type in: git remote add origin
> git@github.com:<username>/first_app.git
> I got no issue.
>
> However, when I type in: git push origin master
> I get an error: fatal: The remote end hung up unexpectedly
>
> I have tried to do that using these instructions:
> http://help.github.com/msysgit-key-setup/
> http://help.github.com/troubleshooting-ssh/
>
> However, when I type in the commands
> ssh
> ssh-keygen
> ssh-keygen -t rsa -C "XXXXXX@XXX.com"
> ssh git@github.com
> ssh -v git@github.com
>
> nothing happens. It just returns a new line. I am attaching a screenshot.
> What am I doing wrong? What do I need to do to get this to work?
> http://old.nabble.com/file/p30829947/screenshot.jpg
Looks like you have no route for port 22 to github.
Are you behind a proxy? If so try https instead.
Is your router blocking 22 outwards? If so, talk to your router admin.
--
Reini Urban
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-02-04 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 20:29 mearrex
2011-02-02 20:34 ` Jeremy Bopp
2011-02-04 6:33 ` Reini Urban [this message]
2011-03-18 19:02 ` sclaussen
2011-03-19 3:47 ` Larry Hall (Cygwin)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTin8YjDU+0bWeDatv-vga4rD9OmC24GunZ9Qj2V3@mail.gmail.com \
--to=rurban@x-ray.at \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).