portscan ignors proxy settings

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set a proxy server
2. Try to portscan the target
3. The scan will be started from the local system

Original issue reported on code.google.com by Andras.T...@gmail.com on 12 Dec 2010 at 7:48

[GoogleCodeExporter]

Hi Andras,

Yes, you're right.
The proxy I tend to use blocks portscans.
However I'm sure plenty wont, so there should be an option as to whether to use 
the proxy settings, and the default should be to use them.

Thanks for reporting this,

Psiinon

Original comment by psii...@gmail.com on 13 Dec 2010 at 10:05

• Changed state: Accepted

[GoogleCodeExporter]

Hi Psiinon!

You may use, tor proxy to test it. 
Proxychains with nmap and tor works grate for me.

Original comment by Andras.T...@gmail.com on 13 Dec 2010 at 10:18

[GoogleCodeExporter]

Will do - thanks!

Original comment by psii...@gmail.com on 13 Dec 2010 at 12:29

[GoogleCodeExporter]

Note -> tor opens a socks4 listener by default on port 9050, so you need to 
configure polipo to listen as an HTTP proxy & forward connections to tor's 
socks4 listener and act as a liaison in that sense. 

While we're at it, I haven't looked into it, but does ZAP proxy your DNS 
queries as well when connecting through an upstrem proxy? I know in a lot of 
circles it's considered an 'information leak' if it queries DNS outside the 
proxy, as one could correlate your DNS queries with the connection times to 
deduce your real IP (potentially). 

Original comment by fitblip@gmail.com on 17 Dec 2010 at 8:56

[GoogleCodeExporter]

I've updated the port scanner to use the proxy by default, and added an option 
to override this if required.

Psiinon

Original comment by psii...@gmail.com on 15 May 2011 at 6:37

• Changed state: Committed

[GoogleCodeExporter]

Fixed in release 1.3.0

Original comment by psii...@gmail.com on 7 Jun 2011 at 5:19

• Changed state: Fixed