Well I tried adding these options to our code:

curl_setopt($ch, CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1);
curl_setopt($ch, CURLOPT_SSL_CIPHER_LIST, "ALL:!aNULL:!LOW:!EXPORT:!SSLv2");

But still got exactly the same error message. It looks like OpenSSL is
just having trouble with its EVP_get_digestbyname calls in the
SSL_CTX_new function, and the "ssl2 md5" one is the first one called no
matter which SSL version is being used. I'll post over on their mailing
list to see if anyone knows more about this.

Thanks again,
Dave

Daniel Stenberg wrote:
> On Thu, 15 Jan 2009, David Justl wrote:
>
>> Thanks for the quick response. I added code to return the OpenSSL
>> error string when this failure occurs (It would be nice if cURL
>> returned this instead of the generic 'Couldn't create a context'
>> error), and this is what I got:
>>
>> error:140A90F1:SSL routines:SSL_CTX_new:unable to load ssl2 md5 routines
>
> We'll welcome patches that improves libcurl in this aspect!
>
>> I'm not sure what could be causing this problem...is there anything
>> that can be done in cURL to help with this? Or do I just need to ask
>> the OpenSSL people?
>
> Since it explictly mentions ssl2 I figure you could try to explictly
> try sslv3 or tlsv1 to work around this. Other than so I don't really
> know...
>
_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-php
Received on 2009-01-16