1 Uncommon Cause of Unknown SSL Protocol Errors in cURL

I came across this error just the other day. cURL throws the following error when I was trying to connect to an https host:

Unknown SSL protocol error in connection to <hostname>:-9846

Connecting to the same host using openssl's s_client, the following error was thrown:

error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac

Turns out, the server my client was trying to connect to was so old, it didn't support TLS! The workaround for this was to force an ssl3 connection.

OpenSSL Version Matrix Updated - October 2014

I updated my OpenSSL Version Matrix again to reflect new versions of OpenSSL released since June 5 2014, including the three new versions of OpenSSL that were released yesterday, (October 15, 2014) to address four security issues.


CryptoNark 0.5.5 Released - Now Supporting Windows

It's only been a few days since the 0.5 release but I've been busy updating CryptoNark with some bug fixes and also added in support for Windows. One caveat: I've only tested this on WIndows 8.1 under a Strawberry Perl 5.18.2 installation. Please let me know if there are any issues on older/newer versions of Strawberry Perl.

One additional item to note in this version. SSLv2 connections to some sites were causing perl to crash when running on Windows. I've modified the subroutine that is making SSLv2 calls to make it more stable but on those sites that it was crashing on, cnark now falsely (?) reports that an sslv2 connection with an RC4-MD5 cipher is possible. I'm still investigating this issue. It does not happen on all sites.

You can download the new CryptoNark v0.5.5 release from the Downloads page and you can see the changelog at the CryptoNark page on this site.