Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- difficulty setting up SOCKS proxy
March 30, 2012, 12:30 am
rate this thread
I'm running cygwin, I understand that after setting up sshd, one can do something
ssh.exe -D *:9970 192.168.1.67 or ssh.exe -D *:9970 184.108.40.206 and it would
then cause ssh.exe to listen, acting as a SOCKS Proxy.
I'm just setting it up locally. But I want to check it with nmap too so I am
binding it to 192.168.1.67(my ip) rather than 127.0.0.1
I can see it listening but when I try to connect to it I get errors like
Error 130 (net::ERR_PROXY_CONNECTION_FAILED): Proxy server connection failed.
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without
sending any data.
And also, curiously, when I try nmap on it, I do this from another machine,
so, it can't see that it's a SOCKS Proxy.
C:\nmap>nmap -P0 -p9970 -sV 192.168.1.67
PORT STATE SERVICE VERSION
9970/tcp open unknown
Re: difficulty setting up SOCKS proxy
ssh -D 0.0.0.0:9970 might be same as *:9970
Chrome needed to be told explicitly that it's a SOCKS proxy..
e.g. socks5://192.168.0.5 where it asks for an IP..
or as the command line switch
C:\Documents and Settings\name\Local Settings\Application
chrome://net-internals/#proxy <-- shows what proxy is set.
As for nmap, it might make assumptions based on port number.. but nmap might
now have a script that can check if a server is a socks proxy.
socks-open-proxy—Checks if an open socks proxy is running on the target.
- » protocol question - issue with exit-status inside unfinished data stream?
- — Newest thread in » Secure Shell Forum