Mac, SSL does not work

sfatula · Post by **sfatula** » Thu Oct 07, 2010 9:27 am

So, I first started off using Macports to install the stable Wine, which means version 1.2 on Macports. The install "worked", and, I could run iexplore to get to the wine home page. However, when I went to run a program I have from a vendor of ours, it failed. Program downloads files from their site using SSL and they won't give me access directly.

The errors is:

err:wininet:NETCON_init failed to load symbol X509_STORE_CTX_get_ex_data
HttpOpenRequest Error 12157 ERROR_INTERNET_SECURITY_CHANNEL_ERROR

So, I figured maybe it was a macports thing, so I tried the devel version. That failed for the same reason.

So, I thought let's try this using the built in iexplore. Sure enough, changing to any SSL page provides the same error message, which tells me it isn't something in the specific program I was trying to run.

So, I tried the osxwinebuilder, same result.

So, I tried the build directly from source (1.3.4) and it also failed for the same reason.

So, I have to conclude it is not the compile method as they all yield the same results. It must be something specific to Mac Snow Leopard perhaps?

Any thoughts on how I might get this to work?

doh123 · Post by **doh123** » Fri Oct 08, 2010 9:34 am

Did you actually get this to work.. like on Linux or something that your expecting it to work? I've never had anything but problems getting SSL stuff to work right, theres many ways it can mess up.

you might need to use a native crypt32 but I'm not entirely sure.

sfatula · Post by **sfatula** » Fri Oct 08, 2010 11:11 am

Sure I did, I reverted way back to 1.1.32. Apparently, there was a change to this made to get the symbol from libcrypto instead of libssl, and, versions before that change seem to work. Seems to be made in 1.1.35.

I wish I knew enough about it for a workaround, but I do not. I'd love to be able to use the current development version with all those new features and updates. Except this one!

doh123 · Post by **doh123** » Fri Oct 08, 2010 4:03 pm

sfatula wrote:Sure I did, I reverted way back to 1.1.32. Apparently, there was a change to this made to get the symbol from libcrypto instead of libssl, and, versions before that change seem to work. Seems to be made in 1.1.35.

I wish I knew enough about it for a workaround, but I do not. I'd love to be able to use the current development version with all those new features and updates. Except this one!

you can file a bug report if it was a regression... get someone to fix it