MacOS X, FreeBSD 9+10 compatilbility about testssl.sh HOT 9 CLOSED

I think you should focus on the OpenSSL version vs the OS version on FreeBSD, simply because most people using the tool will probably use ports to get the latest stable version.
Lots of tools are missing from 0.9.8. I would even recommend using 1.0.2 since it can automatically match the certificate to a hostname, check key exchange ciphers, etc.

from testssl.sh.

@oparoz I would love to but there is this universe called MacOSX ;-( As long as they run this old version and I DONT want those folks to be excluded.... but they get a big warning though.
I am running FreeBSD9 just for OSX compatibility.

The false negatives on BSD flavors here are now only due to sending wrong input over the socket.

from testssl.sh.

Did you try my patch for the socket problem?
oparoz@04ce801

from testssl.sh.

Both lines are included but don't make any difference. Problem is parsing of hexbytes under BSD.

from testssl.sh.

Didn't include the "grep -o" though. Checked and does't help -- would rather try this with sed alone

from testssl.sh.

:( I need to test your version to see what's being sent to the socket. I remember having had to do a lot of tests to make sure the correct sequence was being sent.

from testssl.sh.

@dimitris: Could you do me a favor and do a testssl.sh with MacOSX? I get mostly junk results with plain FreeBSD 9 (no ports).

from testssl.sh.

see attached for comparison

from testssl.sh.

see recent commit 27f06f8 for CCS and heartbleed for MacOSX one needs to open another issue

from testssl.sh.