From 11c143327f998ea0a37dc2e8ad9cf90b97e98c67 Mon Sep 17 00:00:00 2001 From: fyodor Date: Tue, 20 Apr 2010 23:20:24 +0000 Subject: [PATCH] note a couple done tasks --- docs/TODO | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/docs/TODO b/docs/TODO index 3fbf8712c..67921591e 100644 --- a/docs/TODO +++ b/docs/TODO @@ -1,12 +1,6 @@ TODO $Id: TODO 11866 2009-01-24 23:10:05Z fyodor $ -*-text-*- -o Nmap should probably always produce a well-formed XML file, even if - it exits with a fatal() error. In that case, the error should be - included in the XML. Right now, for example, if the network is - down, the XML output will just stop (no closing tags) and Nmap will - print something to STDERR like: - nexthost: failed to determine route to 9.48.184.164 - QUITTING! +o Upgrade libpcap to the new 1.1.1 version. o Finish selecting GSoC 2010 projects @@ -52,13 +46,6 @@ o We should probably enhance scan stats--maybe we can add a full-scan completion time estimate? Some ideas here: http://seclists.org/nmap-dev/2010/q1/1007 -o We should have a standard function which takes time arguments in the - same format as Nmap does (e.g. 60s, 1m, etc.) and the scripts which - take time arguments should be modified to use it. David suggests - this here: http://seclists.org/nmap-dev/2010/q2/35. We are also - going to update the normal Nmap timing functions to take seconds by - default, as described here: http://seclists.org/nmap-dev/2010/q2/159 - o [NSE] Consider modifying our brute force scripts to take advantage of the new NSE multiple-thread parallelism features. @@ -539,6 +526,21 @@ o random tip database DONE: +o We should have a standard function which takes time arguments in the + same format as Nmap does (e.g. 60s, 1m, etc.) and the scripts which + take time arguments should be modified to use it. David suggests + this here: http://seclists.org/nmap-dev/2010/q2/35. We are also + going to update the normal Nmap timing functions to take seconds by + default, as described here: http://seclists.org/nmap-dev/2010/q2/159 + +o Nmap should probably always produce a well-formed XML file, even if + it exits with a fatal() error. In that case, the error should be + included in the XML. Right now, for example, if the network is + down, the XML output will just stop (no closing tags) and Nmap will + print something to STDERR like: + nexthost: failed to determine route to 9.48.184.164 + QUITTING! + o Get @output sections for the last remaining scripts w/o them: [WARN] script auth-spoof missing @output [WARN] script db2-das-info missing @output