PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2026-01-15 19:09:01 +00:00
Code Issues Projects Releases Wiki Activity

Document --proxies option.

Browse Source
This commit is contained in:
henri
2013-08-17 11:47:42 +00:00
parent 59e68ddffb
commit 179451f485
1 changed files with 38 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
docs/refguide.xml
View File

@@ -3434,6 +3434,44 @@ work properly.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--proxies <replaceable>Comma-separated list of proxy
URLs</replaceable></option> Relay TCP connections via a chain of
proxies.
<indexterm significance="preferred"><primary><option>--proxies</option></primary></indexterm>
<indexterm><primary>proxy</primary></indexterm>
<indexterm><primary>proxies</primary></indexterm>
</term>
<listitem>
<para>Asks Nmap to establish TCP connections via the supplied chain of
<indexterm><primary>proxies</primary></indexterm>. Connections are
established to the first node of the chain, which is in turn asked to
connect to the second one... to eventually reach the target. This
technique degrades performance, mostly by introducing latency. It is
up to the user to adjust timeouts and other scan parameters
accordingly when invoking nmap. Typically, some proxies might refuse
to handle as many concurrent connections as nmap's default
parallelism.</para>
<para>The option takes a list of proxies as argument, expressed as
URLs like <literal>proto://host:port</literal>. Use commas to separate
node URLs of a chain. No authentication is supported yet. Valid
protocols are <literal>HTTP</literal> and <literal>SOCKS4</literal>.
</para>
<para>Warning: this feature is still under development and has
limitations. It is implemented within the nsock library and thus has
no effect on the ping, port scanning and OS discovery phases. Only
NSE and version scan already benefit from this option. Also, SSL
connections are not supported yet, as well as proxy-side DNS
resolving (hostnames are always resolved by nmap). In other words,
the current implementation does not aim to provide strong
anonymity.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--badsum</option> (Send packets with bogus TCP/UDP checksums)