[PATCHed] Fix --max-os-tries and --max-rtt-timeout options

[Kris Katterjohn <katterjohn () gmail com>]

The attached patch (/nmap SVN r4409) fixes the --max-os-tries and
--max-rtt-timeout options. The SVN log explains:

------------------------------------------------------------------------
r4409 | kris | 2007-01-28 07:18:32 -0600 (Sun, 28 Jan 2007) | 1 line

Fix --max-os-tries and --max-rtt-timeout options. There was a typo which
caused two optcmp()s to be checking for max-rtt-timeout instead of one
for that and one for max-os-tries. Since the first one was supposed to
check for max-os-tries, --max-rtt-timeout has been setting max-os-tries.
This meant there was no way to set max-rtt-timeout, and --max-os-tries
always failed with an error message.
------------------------------------------------------------------------

Thanks,
Kris Katterjohn

Index: nmap.cc
===================================================================
--- nmap.cc     (revision 4408)
+++ nmap.cc     (revision 4409)
@@ -637,7 +637,7 @@
                o.scriptupdatedb = 1;
        } else
 #endif
-       if (optcmp(long_options[option_index].name, "max-rtt-timeout") == 0) {
+       if (optcmp(long_options[option_index].name, "max-os-tries") == 0) {
        l = tval2msecs(optarg);
        if (l < 1 || l > 50) 
          fatal("Bogus --max-os-tries argument specified, must be between 1 and 50 (inclusive)");


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org