From: "Dennis" <dennisfm@friendlymatch.com>
To: "Shawn Pearce" <spearce@spearce.org>
Cc: <git@vger.kernel.org>
Subject: Re: Setting up Git Server over SSH
Date: Mon, 15 Nov 2010 14:14:46 -0500 [thread overview]
Message-ID: <E698106BE2EB405A93D2C3304AF79529@denny> (raw)
In-Reply-To: AANLkTimF2N-rYFYjOMm5kRRqRueLnmzJGpUoaCK3jsAC@mail.gmail.com
Thanks, that worked
I used OpenSSH instead of Putty
and that fixed things up.
Dennis
----- Original Message -----
From: "Shawn Pearce" <spearce@spearce.org>
To: "Dennis" <dennisfm@friendlymatch.com>
Cc: <git@vger.kernel.org>
Sent: Monday, November 15, 2010 1:38 PM
Subject: Re: Setting up Git Server over SSH
> On Mon, Nov 15, 2010 at 10:20 AM, Dennis <dennisfm@friendlymatch.com>
> wrote:
>> I am doing this, but it fails:
>>
>>> git clone ssh://hostname.com:/home/user/.git
>>
>> Cloning into user...
>> fatal: protocol error: bad line length character: logi
>
> This looks to me like your server is echoing back text upon login.
> That text is being confused for Git protocol data by the Git client,
> but its not as expected, so it aborts with an error message.
>
> Try getting the simple case to work first:
>
> ssh hostname.com echo hello
>
> This should *only* print "hello". If it prints anything else (and
> right now I suspect it prints "login ..."), that will confuse Git.
> You need to adjust your server's shell login scripts to stop echoing
> information during a non-interactive shell. Or you may need to adjust
> your SSH client to ensure the authentication proceeds smoothly. Those
> "Access denied" errors look like you aren't actually authenticating to
> the server.
>
> --
> Shawn.
next prev parent reply other threads:[~2010-11-15 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 18:20 Setting up Git Server over SSH Dennis
2010-11-15 18:38 ` Shawn Pearce
2010-11-15 19:14 ` Dennis [this message]
2010-11-16 10:46 ` Ævar Arnfjörð Bjarmason
2010-11-17 2:25 ` Dennis
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=E698106BE2EB405A93D2C3304AF79529@denny \
--to=dennisfm@friendlymatch.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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