PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2026-02-13 00:46:32 +00:00
Code Issues Projects Releases Wiki Activity

note a couple done tasks

Browse Source
This commit is contained in:
fyodor
2010-04-20 23:20:24 +00:00
parent 701fe380f8
commit 11c143327f
1 changed files with 16 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
docs/TODO
View File

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