From 15e2997e669ca64701c1f64398f08567bd2ba3b2 Mon Sep 17 00:00:00 2001 From: venkat Date: Mon, 27 Jul 2009 23:44:07 +0000 Subject: [PATCH] Added entry for wildcard SSL certificate support to Ncat --- CHANGELOG | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CHANGELOG b/CHANGELOG index f269f8050..1072c8599 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,5 +1,13 @@ # Nmap Changelog ($Id$); -*-text-*- +o [Ncat] Now Ncat supports wildcard SSL certificates too.Wildcard character(*) can + be in commonname field or in DNS field of Subject Alternative Name(SAN) + Extension of SSL certificate. + Wildcard Matching Rules: + -'*' should be only on the leftmost component of FQDN.(*.example.com but not www.*.com or www.example*.com). + -The leftmost component should contain only '*' and it should be followed by '.'(*.example.com but not *w.example.com or w*.example.com). + -There should be atleast three components in FQDN.(*.exmaple.com but not *.com or *.com.).[venkat] + o Nmap now handles the case when a primary network interface (venet0) does not have an address assigned but its aliases do (venet0:1 etc.). This could result in the error messages