CERBERUS/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2026-08-27 03:48:14 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Just moving an item

Browse source
This commit is contained in:
fyodor 2010-04-04 19:42:03 +00:00
parent 3b34c84de7
commit 2f59126185
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/TODO
View file

@ -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