docs/TODO

@@ -75,6 +75,15 @@ o [NSE] We need to deal with libraries which improperly use global
   long history of bugs caused by non-local variables defined in NSE
   libraies and often causing deadlocks.
 
+o [NSE] Allow spaces in script arguments without the user having to
+  manually quote them (beyond normal shell escape quoting).  See:
+  http://seclists.org/nmap-dev/2009/q3/0090.html
+
+o [NSE] Consider integrating HP Laserjet PJL status-setting script.
+  See this thread for an example of such a script:
+  http://seclists.org/nmap-dev/2009/q3/0083.html (note that it is
+  updated during the thread).
+
 o Consider the open proxy scripts more carefully
  - How should we test whether the proxy attempt was successful?  Right
    now we look for a google-specific Server header after trying to
@@ -119,10 +128,13 @@ o [Web] Consider adding training/introduction videos to the Nmap site
    introduction to each tool (Nmap, Zenmap, Ncat, Ndiff) on its web
    page.
  o They need to be good to be useful--the sort of the quality you see
-   in Laura Chappell's Wireshark videos or James Messer's Nmap videos.
+   in Laura Chappell's Wireshark videos or James Messer's Nmap videos
+   or Irongeek's videos (http://www.irongeek.com).
  o Besides the promotional videos, users would probably enjoy more
    in-depth video instructions (e.g. covering the Nmap Network
    Scanning topics).
+ o Here's an example product page with lots of videos (we may not go
+   that far): http://www.splunk.com/product
 
 o [Ncat] In verbose mode, I'd like to see clock time and maybe in/out
   traffic stats when a client connection ends.  Maybe it could use a
@@ -590,7 +602,8 @@ o Separate nbase into its own Windows library in the same way as Andy did
 o Look into iplog ( http://ojnk.sourceforge.net/ ) -z option which is 
   supposed to fool OS detection.
 
-o security audit of Nmap code
+o More security auditing of Nmap code (it never hurts to do more proactive
+  security auditing).
 
 o Nmap / Nmap-hackers FAQ