From e5b1214a73e56ecb7e59dbb554d9144bf1b43328 Mon Sep 17 00:00:00 2001 From: dmiller Date: Mon, 10 Nov 2014 16:16:31 +0000 Subject: [PATCH] Note a done infrastructure task --- todo/done.txt | 8 ++++++++ todo/nmap.txt | 8 -------- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/todo/done.txt b/todo/done.txt index 540c87b68..9b84d540c 100644 --- a/todo/done.txt +++ b/todo/done.txt @@ -1,5 +1,13 @@ DONE: +o Web: We should probably distribute RapidSSL intermediate certificate + on SecWiki so it is trusted even if browsers don't have that cert + cached. Here's a page nothing the issue: + https://www.ssllabs.com/ssltest/analyze.html?d=secwiki.org + - We probably need to add an entry in apache conf after + SSLCertificateFile which looks something like: + SSLCertificateChainFile /etc/apache2/rapidssl.pem + o The XML version of Nmap lists and describes the six port states recognized by Nmap near the top of the "Port Scanning Basics" section.  That can be seen in the HTML rendering at diff --git a/todo/nmap.txt b/todo/nmap.txt index 03b8e87da..3de7cf87e 100644 --- a/todo/nmap.txt +++ b/todo/nmap.txt @@ -132,14 +132,6 @@ o When scanning your own IP from Windows, Nmap currently recognizes in this case (e.g. do a connect scan, etc.). See http://seclists.org/nmap-dev/2013/q3/519 -o Web: We should probably distribute RapidSSL intermediate certificate - on SecWiki so it is trusted even if browsers don't have that cert - cached. Here's a page nothing the issue: - https://www.ssllabs.com/ssltest/analyze.html?d=secwiki.org - - We probably need to add an entry in apache conf after - SSLCertificateFile which looks something like: - SSLCertificateChainFile /etc/apache2/rapidssl.pem - o Investigate Checkmarx static analysis report of Nmap source tree that someone sent us on Feb 12. It looks like mostly false positives, but we should go through to check for any real bugs or even possible