Nmap Development mailing list archives
Re: nsock SSL error with SOC5
From: Fyodor <fyodor () insecure org>
Date: Wed, 22 Aug 2007 20:35:08 -0700
On Wed, Aug 22, 2007 at 07:29:49PM -0600, David Fifield wrote:
On Wed, Aug 22, 2007 at 02:38:51PM -0500, DePriest, Jason R. wrote:The error comes after the port scans and during the service scan: nsock_connect_ssl called - but nsock was built w/o SSL support. QUITTINGI figured it out. It turns out the nsock configure script does the check for HAVE_OPENSSL, but never defines it in a header file if it finds it. So why did it work before? HAVE_OPENSSL used to be defined in nbase/nbase_config.h also, and that's where nsock got it from. r5242 in /nmap-exp/soc07/nbase and r5493 in /nbase (when it was merged) removed the check for HAVE_OPENSSL from nbase (because it's not used there) and that's what broke things. I just committed a change to nsock that ought to fix it.
Wonderful! Thanks David. Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- nsock SSL error with SOC5 DePriest, Jason R. (Aug 22)
- Re: nsock SSL error with SOC5 DePriest, Jason R. (Aug 22)
- Re: nsock SSL error with SOC5 Brandon Enright (Aug 22)
- Re: nsock SSL error with SOC5 David Fifield (Aug 22)
- Re: nsock SSL error with SOC5 Fyodor (Aug 22)
- Re: nsock SSL error with SOC5 DePriest, Jason R. (Aug 23)
- Re: nsock SSL error with SOC5 David Fifield (Aug 23)
- Re: nsock SSL error with SOC5 DePriest, Jason R. (Aug 23)