From dc7d16ca4c20188e9a53f24a5f0fb7b6940d6509 Mon Sep 17 00:00:00 2001 From: dmiller Date: Tue, 21 Oct 2014 05:50:37 +0000 Subject: [PATCH] Note a done task --- todo/done.txt | 10 ++++++++++ todo/nmap.txt | 10 ---------- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/todo/done.txt b/todo/done.txt index 3d4121a65..ce5d23e24 100644 --- a/todo/done.txt +++ b/todo/done.txt @@ -1,5 +1,15 @@ DONE: +o Fix a segmentation fault in Ncat when scanned with the SSL NSE + scripts. I was able to reproduce this on 2013-09-27 with latest SVN + by running: + Ncat: ncat -v -k --ssl -l localhost + Nmap: ./nmap --script-trace --script '+ssl*' localhost -p 31337 + This was initially reported by Timo Juhani Lindfors on the Debian + bug tracker: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724580 + Henri notes: "I traced the latter back to openssl and opened a + ticket there, which never got any reply... https://rt.openssl.org/Ticket/Display.html?id=2885&user=guest&pass=guest" + o Investigate how we're ending up with OS fingerprints in nmap-os-db with attribute names like W0 and W8 when according to the docs they are only supposed to be W1 - W6 (and plain W). diff --git a/todo/nmap.txt b/todo/nmap.txt index 4d0712e6c..b659b88c3 100644 --- a/todo/nmap.txt +++ b/todo/nmap.txt @@ -210,16 +210,6 @@ o We should fix service detection so it can handle 0-byte captures without crashing. See http://seclists.org/nmap-dev/2014/q2/105 -o Fix a segmentation fault in Ncat when scanned with the SSL NSE - scripts. I was able to reproduce this on 2013-09-27 with latest SVN - by running: - Ncat: ncat -v -k --ssl -l localhost - Nmap: ./nmap --script-trace --script '+ssl*' localhost -p 31337 - This was initially reported by Timo Juhani Lindfors on the Debian - bug tracker: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724580 - Henri notes: "I traced the latter back to openssl and opened a - ticket there, which never got any reply... https://rt.openssl.org/Ticket/Display.html?id=2885&user=guest&pass=guest" - o Our http library should allow the client to specify a max size in advance and should probably enforce some sort of maximum by default (unless turned off by the script). That way sites can't DoS Nmap by