Nmap Development mailing list archives
Re: GSOC 2012
From: SAI LAKSHMI Bhavana <oslbhavana () gmail com>
Date: Thu, 29 Mar 2012 17:17:03 +0530
Hello Sir, Thank you very much for your valuable suggestions. I am thinking of having a design like this nmap -sT <target> --proxy socks4a://proxy1:9100/ --proxy http://proxy2:8080/ --proxy socks5://proxy3:3128/ Make a nsockpool with several events such as 1)a connect event which is used to connect to proxy1. 2)a write event which sends the CONNECT request "connect http://proxy2:8080 HTTP/1.0" through handle_write_result; 3)a read event to verify the success(from iobuf) of the request. the steps 2 ,3 will be repeated until a Connect request is sent to the <target> and verified. the request to be sent for a particular proxy HTTP or SOCKS can be known from two methods that can be included namely req_http_proxy(url ), req_socks_proxy(url) Yes there will be another function such as nsock_connect_tcp_primitive() that simply does connect(). Suggestions are welcomed :) _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- GSoC 2012 Zisis Sialveras (Feb 09)
- Re: GSoC 2012 David Fifield (Mar 17)
- <Possible follow-ups>
- GSOC 2012 SAI LAKSHMI Bhavana (Mar 20)
- Re: GSOC 2012 David Fifield (Mar 20)
- Re: GSOC 2012 SAI LAKSHMI Bhavana (Mar 22)
- Re: GSOC 2012 David Fifield (Mar 22)
- Re: GSOC 2012 SAI LAKSHMI Bhavana (Mar 29)
- Re: GSOC 2012 David Fifield (Mar 29)
- Re: GSOC 2012 David Fifield (Mar 20)