From 2f59126185b7867dd7b648a15eb1b8840dd7d9ac Mon Sep 17 00:00:00 2001 From: fyodor Date: Sun, 4 Apr 2010 19:42:03 +0000 Subject: [PATCH] Just moving an item --- docs/TODO | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/TODO b/docs/TODO index a8cb7a783..b7d79b6dd 100644 --- a/docs/TODO +++ b/docs/TODO @@ -1,5 +1,13 @@ 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 Brainstorm for GSoC 2010 ideas and fill out the org application by Friday 3/12 4PM PST. o NSE scripts @@ -32,14 +40,6 @@ o Remove --interactive. It was broken for a long time and nobody the documentation complexity of people having to read and learn about a feature they are unlikely to ever use. -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 [NSE] Maybe we should create a class of scripts which only run one time per scan, similar to auxiliary modules in Metasploit. We already have script classes which run once per port and once per