Nmap Development mailing list archives
Re: ncat ssl client doesn't support Server Name Indication extension (SNI)
From: David Fifield <david () bamsoftware com>
Date: Fri, 16 Jul 2010 09:44:19 -0600
On Thu, Jul 15, 2010 at 01:12:08PM +0100, Nuno Gonçalves wrote:
Ncat ssl client doesn't support Server Name Indication extension according to RFC 4366. http://en.wikipedia.org/wiki/Server_Name_Indication This way it doesn't allow to connect to web servers that have more than one virtual host on the same IP address.
That web page says that SNI is supported by OpenSSL. Do you happen to know how to enable it? Maybe it is only a matter of an additional function call. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- ncat ssl client doesn't support Server Name Indication extension (SNI) Nuno Gonçalves (Jul 15)
- Re: ncat ssl client doesn't support Server Name Indication extension (SNI) David Fifield (Jul 16)
- Re: ncat ssl client doesn't support Server Name Indication extension (SNI) Nuno Gonçalves (Jul 16)
- Re: ncat ssl client doesn't support Server Name Indication extension (SNI) David Fifield (Jul 16)
- Re: ncat ssl client doesn't support Server Name Indication extension (SNI) David Fifield (Aug 13)
- Re: ncat ssl client doesn't support Server Name Indication extension (SNI) Nuno Gonçalves (Jul 16)
- Re: ncat ssl client doesn't support Server Name Indication extension (SNI) David Fifield (Jul 16)