Git致命：远端挂断 [英] Git fatal: remote end hung up

问题描述

当前设置

URL：ssh：// user @ host：port / myapp.git

已经运行腻子 - 并且可以通过〜/ .ssh / authorized_keys直接使用有效的.ppk键进行连接。在Git和TortoiseGIT中 - 我同时使用plink.exe。

Putty工作正常 - 没有问题 - 但是当我将该URL运行到bash时，我得到了一个git clone（url）
$ b

致命：远程终端预期挂断

在cygwin bash终端中 - 运行ssh user @ host - 根本就不会运行probs。

任何人都会提出任何建议吗？

解决方案

我发现使用sit.exe从Git包每次工作，而不是cygwin自带的ssh（默认）。
使用这个导出的变量似乎有帮助;它比较慢（2倍或更多），但更稳定。

$ export GIT_SSH = / cygdrive / c / Program \ Files / Git / bin / ssh.exe
将其作为另一个解决方法。

供参考：
此版本的Msysgit附带OpenSSH 4.6p1，OpenSSL 0.9.8e。 [作品]
Cygwin的SSH是OpenSSH 5.5p1，OpenSSL 0.9.8n。 [不起作用]

So I thought I had finally got everything setup on Windows ... then ran into this issue.

Current setup

URL: ssh://user@host:port/myapp.git

Already run Putty - and can connect using valid .ppk keys through the ~/.ssh/authorized_keys direct. In Git and TortoiseGIT - I set both to use "plink.exe".

Putty works fine - no issues - but when I run that URL into bash I get for a git clone (url)

fatal: the remote end hung up expectedly

In a cygwin bash terminal - running "ssh user@host" - works no probs at all.

Anyone suggest anything?

解决方案

I found out that using ssh.exe from the Git package works every time, as opposed to the ssh that comes with cygwin (the default). Using this exported variable seems to help; it's slower (2x or more) but it's more stable. Take it as another workaround.

$ export GIT_SSH=/cygdrive/c/Program\ Files/Git/bin/ssh.exe

FYI: This version of Msysgit comes with OpenSSH 4.6p1, OpenSSL 0.9.8e. [works] Cygwin's SSH is OpenSSH 5.5p1, OpenSSL 0.9.8n. [doesn't work]

这篇关于Git致命：远端挂断的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！