Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

RE: Pubic key with proxy command

Subject: RE: Pubic key with proxy command
Date: Mon, 2 Jul 2007 12:44:39 -0400
Darren,

Yes it working! as the tcs_wrapper was relaxed for my proxy's external IP.
Thanks for your great help.

Thanks & Regards,
Balaji Mariyappan
GE Equipment services
Desk: 312.853.5056
Mobile: 312.213.7112




-----Original Message-----
From: listbounce@securityfocus.com
[mailto:listbounce@securityfocus.com]On Behalf Of Darren Tucker
Sent: Sunday, July 01, 2007 10:14 PM
To: Mariyappan, Balaji (GE Indust, ES RAIL, consultant)
Cc: secureshell@securityfocus.com
Subject: 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.

<Prev in Thread] Current Thread [Next in Thread>