I've seen this question asked before and have tried the solutions
posted to no avail. I can get ssh-1.2.26 to go through a firewall
but not ssh-2.0.9 or ssh-2.0.11. Is there a fundamental reason for
this or am I doing something wrong?

The machine I am trying to connect to is running ssh-2.0.9 and
will not accept a ssh-1.2.26 request.

ssh-1.2.26:
--------------------------------------------
runsocks ssh -v yyy.yyy.com
SSH Version 1.2.26 [i686-unknown-linux], protocol version 1.5.
Standard version.  Does not use RSAREF.
horta: Reading configuration data /etc/ssh_config
horta: ssh_connect: getuid 1449 geteuid 1449 anon 1
horta: Connecting to  yyy.yyy.com [xxx.xxx.xxx.xxx] port 22.
horta: Connection established.
horta: Remote protocol version 2.0, remote software version 2.0.9
horta: Waiting for server public key.
Connection closed by remote host.

ssh-2.0.9:
--------------------------------------------
runsocks ssh2 -v yyy.yyy.com
debug: hostname is 'yyy.yyy.com'.
Unrecognized configuration parameter ssh1agentcompatibility
debug: connecting to yyy.yyy.com...
debug: entering event loop
FATAL: TCP/IP Failure

I have set the SSH_SOCKS_SERVER env variable to:
socks:[EMAIL PROTECTED]:1080/15.0.0.0/8,127.0.0.0/8

I am using this line to configure (it has a mix of ssh1 and ssh2 flags
by now):
configure --enable-debug --enable-socks
    --with-socks4=socks-server.cup.hp.com
    --with-socks-server=socks-server.cup.hp.com

I know that my socks server is socks4, but my library is libsocks5,
could that
be the problem? How do you tell ssh2.0.9 to use the socks libray but use
4 not
5?

Any other ideas? Has anyone actually gotten this to work through a
firewall?
Thanks, pete


Reply via email to