Index of /ORBman/tmp/nmap

      Name                                   Last modified       Size  Description


[DIR] Parent Directory                       14-Dec-2009 15:15      -  
[TXT] nmap-3.81-osscan_no_ports_reuse.patch  09-Dec-2005 13:49     1k  
[TXT] nmap-3.95-CONNECT-closedfiltered.patch 09-Dec-2005 13:49     2k  
[TXT] nmap-3.95-detect_TARPIT.patch          04-Mar-2006 09:28     7k  
[TXT] nmap-4.03-defeat_ratelimits.patch      14-May-2006 10:52    10k  
[TXT] nmap-4.03-sf_MSDTCvSSL.patch           14-May-2006 09:35     1k  
[TXT] nmap-4.04-detect_TARPIT.patch          01-Jun-2006 12:13     6k  
[DIR] old/                                   14-May-2006 09:46      -  

Patches apply to Nmap 4.03 in this order:

nmap-4.03-sf_MSDTCvSSL.patch
nmap-4.03-defeat_ratelimits.patch
nmap-3.95-CONNECT-closedfiltered.patch
nmap-3.95-detect_TARPIT.patch
nmap-3.81-osscan_no_ports_reuse.patch

You don't have to apply *all* of them, anyway.
Only defeat_ratelimits and detect_TARPIT should be interesting.

TODO
1) Make relevant updates to man page.
   (http://www.insecure.org/nmap/data/nmap-man.xml)
2) osscan_no_ports_reuse.patch breaks -g and messes with o.magic which is
   "supposed" to be read-only
3) defeat_ratelimit could be considered as a "dirty hack" because it makes
   too much "blind" assumptions about logic outside the scope of the code it is
   changing. For example, if there is a new functionality in Nmap that
   distinguishes between different PORT_FILTERED cases ("ICMP Unreachable"
   versus "no response") this patch would could break it in a sort of way...
  (On the other side, I don't think it is worth trying to make it cleaner
   in the meantime because ratelimit logic will probably use that functionality too)