git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: Chanakya Vattikuti <gk2cveragon1@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Error
Date: Wed, 10 Jul 2013 19:15:59 +0400	[thread overview]
Message-ID: <20130710191559.a0236010ffccbdd526d4d69c@domain007.com> (raw)
In-Reply-To: <632ECB1A-63EA-4334-8716-53A1F45B6E0B@gmail.com>

On Tue, 9 Jul 2013 20:30:37 -0500
Chanakya Vattikuti <gk2cveragon1@gmail.com> wrote:

> I get this error message when trying to create a shared ssh key in
> Mac osx Lion

This problem has nothing to do with Git as it purely is about
transferring a public part of your SSH key to another host.
So try asking on the OS support channels.

> scp .ssh/id_rsa.pub cvattiku@cook.cs.uno.edu:~/
> ssh_exchange_identification: Connection closed by remote host
> lost connection

Since the public part of your key is not transferred to that remote host
yet, and it is not registered as a trusted key there, you have to use
an SSH authentication method other than "publickey".  Or, if you have
another SSH key which is registered as trusted on the remote host, you
might try to use it explicitly using the "-i <private_key_file_>"
command-line option to `scp`.

If this fails or not applicable, at least try to run `scp` with
multiple "-v" command-line options (like `scp -vvvv ...`) to get
extensive details about authentication protocols it tried with the
server and which of them were agreed upon by both sides and tried.

It might turn out that the server only accepts publickey authentication
mechanism, and so you are not able to upload and register your public
key yourself (chicken and egg problem).  In that case, contact the
server's system administrator for assistance.

If the server has certain "Git hosting" solution like Gitlab, you might
need to try registering your key using some other means like logging to
your Git account via some web interface and pasting the key there --
just like you'd do this on github.

If studying that information won't help you, provide it when you will
be asking this question on the Mac OS support channels.

  reply	other threads:[~2013-07-10 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10  1:30 Error Chanakya Vattikuti
2013-07-10 15:15 ` Konstantin Khomoutov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-22 23:02 error Luciano Schillagi
2016-09-23  4:46 ` error Jeff King
     [not found] <CAK99BNA_2hwgkLUap_ThOG8drWkP6f74hdW=SNq_DpuNW=j2ew@mail.gmail.com>
     [not found] ` <C1F7B566-69F4-4A22-89EA-59B24677DF43@gmail.com>
2016-10-04 17:27   ` error Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130710191559.a0236010ffccbdd526d4d69c@domain007.com \
    --to=kostix+git@007spb.ru \
    --cc=git@vger.kernel.org \
    --cc=gk2cveragon1@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).