mailing list archives
Re: nsock_connect_ssl: bad version identification?
From: Fyodor <fyodor () insecure org>
Date: Fri, 16 May 2008 14:22:00 -0700
On Thu, May 15, 2008 at 09:02:53PM +0200, mixter () gmail com wrote:
I'm trying to establish a SSL connection using nsock_connect_ssl(),
I get "Did not receive identification string" (using nmap -sV with ssl
"Bad protocol version identification '\200\177\001\003\001' from 127.0.0.1"
(the latter with my usage of nsock_connect_ssl():
nmap-exp/ncat/ncat_main.c line 471).
So Nmap -sV is not working for you against SSL servers? What happens
if you take the Nmap 4.62 release and do this command?
# nmap -PN -sV -p443 google.com
Starting Nmap 4.62 ( http://nmap.org ) at 2008-05-16 14:19 PDT
Warning: Hostname google.com resolves to 3 IPs. Using 220.127.116.11.
Interesting ports on eh-in-f99.google.com (18.104.22.168):
PORT STATE SERVICE VERSION
443/tcp open ssl/http Google httpd 1.3 (GFE)
Service Info: OS: Linux
Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 13.215 seconds
What OS and OpenSSL version are you using?
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org