Re: Pubic key with proxy command

Mariyappan, Balaji (GE Indust, ES RAIL, consultant) wrote:
> I'm getting following message when connecting to a external sftp
> server by public key authendication and through a ssh proxy.
[...]
> DEBUG: begin_http_relay()
> DEBUG: >>> "CONNECT 207.106.160.143:22 HTTP/1.0\r\n"
> DEBUG: >>> "\r\n"
> DEBUG: <<< "HTTP/1.0 200 Connection established\r\n"
> DEBUG: connected, start user session.
> DEBUG: <<< "\r\n"
> DEBUG: connected
> DEBUG: start relaying.
> DEBUG: connection closed by peer
> DEBUG: relaying done.
> DEBUG: that's all, bye.

This output is from the proxycommand, and it indicates that the proxy is 
disconnecting immediately for some reason, possibly because the server 
is not listening on port 22 or the SSH server is dropping the connection 
immediately (the latter is usually caused by tcpwrappers on the server).

Try running the proxy command on its own.  Unless you see 
"SSH-something" then the problem is with either the proxy or the SSH 
server and not the client.

> ssh_exchange_identification: Connection closed by remote host
[...]
> What is the problem why it "debug3: Not a RSA1 key"
> Some one please try to clarify me.

That's normal, it tries to read it as a RSA1 key before trying it as a 
v2 key.

> I'm using OpenSSH_4.3p2, OpenSSL 0.9.8a...

--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.