'svn+ssh10401'挂在普通的“ssh”位置有效,但无法进入“协议 2.0”;

发布于 2024-12-23 20:10:18 字数 1782 浏览 4 评论 0原文

在非标准端口上通过 ssh 建立隧道,因为我必须在远程服务器上的端口 10401(它是“svnserve”)上运行 svn,所以我在有关协议 2.0 的日志行应该是:

Local box uname: Linux localbox 之前遇到了问题3.0.0-14-generic #23-Ubuntu SMP 2011 年 11 月 21 日星期一 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

远程主机 unname (服务器名称更改为 'foo'): Linux foo 2.6.32.27-grsec #5 SMP Thu Dec 30 01:24:01 PST 2010 i686 未知 未知 GNU/Linux

christopherbalz@localbox:~$ svn co --username=christopherbalz svn+ssh10401://foo.bar.com/baz

OpenSSH_5.8p1 Debian-7ubuntu1, OpenSSL 1.0.0e 6 Sep 2011
debug1: Reading configuration data /home/christopherbalz/.ssh/config
debug1: Applying options for foo.bar.com
debug1: Applying options for foo.bar.com
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to foo.bar.com [208.95.105.37] port 10401.
debug1: Connection established.  
debug1: identity file /home/christopherbalz/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/christopherbalz/.ssh/id_rsa-cert type -1
debug1: identity file /home/christopherbalz/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/christopherbalz/.ssh/id_rsa-cert type -1

< hangs here forever >

相比之下,一个简单的ssh 到该服务器会直接给出与上面相同的日志加上这个(以及更多,不粘贴在这里)之后,就在上面日志挂起的地方:

debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8
debug1: match: OpenSSH_5.8 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
. . . 

由于“协议2.0”日志直接出现在之后,我想知道在svn + ssh下日志中提到的兼容模式是否存在一些问题?如果是这样,如何解决该问题?如果不是,可能是什么原因导致此挂起?

Tunneling through ssh on a non-standard port, as I must run svn on my remote server on port 10401 (it's 'svnserve'), I get a hang right before where log lines about protocol 2.0 should be:

Local box uname: Linux localbox 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Remote box unname (server name changed to 'foo'): Linux foo 2.6.32.27-grsec #5 SMP Thu Dec 30 01:24:01 PST 2010 i686 unknown unknown GNU/Linux

christopherbalz@localbox:~$ svn co --username=christopherbalz svn+ssh10401://foo.bar.com/baz

OpenSSH_5.8p1 Debian-7ubuntu1, OpenSSL 1.0.0e 6 Sep 2011
debug1: Reading configuration data /home/christopherbalz/.ssh/config
debug1: Applying options for foo.bar.com
debug1: Applying options for foo.bar.com
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to foo.bar.com [208.95.105.37] port 10401.
debug1: Connection established.  
debug1: identity file /home/christopherbalz/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/christopherbalz/.ssh/id_rsa-cert type -1
debug1: identity file /home/christopherbalz/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/christopherbalz/.ssh/id_rsa-cert type -1

< hangs here forever >

By contrast, a plain ssh to this server gives the same log as above plus this (and more, not pasted here) directly after, right where the log hangs above:

debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8
debug1: match: OpenSSH_5.8 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
. . . 

Since the 'protocol 2.0' logs come directly after, I wonder if under svn+ssh there is some issue with the compatibility mode mentioned in the logs? If so, how to troubleshoot that? If not, what might be causing this hang?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文