Nmap Development mailing list archives
[PATCH] Remove "force" from NmapOps
From: Kris Katterjohn <kjak () ispwest com>
Date: Sat, 30 Sep 2006 09:12:05 -0500
The attached patch removes the unused variable "force" from NmapOps. It's a diff against 4.20ALPHA7 Thanks, Kris Katterjohn
--- x/NmapOps.cc 2006-08-28 22:26:10.000000000 -0500
+++ y/NmapOps.cc 2006-09-29 20:45:46.000000000 -0500
@@ -229,7 +229,7 @@ void NmapOps::Initialize() {
listscan = pingscan = allowall = ackscan = bouncescan = connectscan = 0;
rpcscan = nullscan = xmasscan = fragscan = synscan = windowscan = 0;
maimonscan = idlescan = finscan = udpscan = ipprotscan = noresolve = 0;
- force = append_output = 0;
+ append_output = 0;
memset(logfd, 0, sizeof(FILE *) * LOG_NUM_FILES);
ttl = -1;
badsum = 0;
--- x/NmapOps.h 2006-08-28 22:26:10.000000000 -0500
+++ y/NmapOps.h 2006-09-29 20:45:49.000000000 -0500
@@ -281,7 +281,6 @@ class NmapOps {
int windowscan;
int xmasscan;
int noresolve;
- int force; /* force nmap to continue on even when the outcome seems somewhat certain */
int append_output; /* Append to any output files rather than overwrite */
FILE *logfd[LOG_NUM_FILES];
FILE *nmap_stdout; /* Nmap standard output */
_______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- [PATCH] Remove "force" from NmapOps Kris Katterjohn (Sep 30)
