Sebastian Brückner schrieb:
> As far as I can see the certificate itself is not the problem. Since I
> insert it directly using OpenSSL functions curl probably doesn't even
> know its there. That might be the problem: I guess curl assumes that for
> CURLOPT_VERIFYPEER to work it needs certificates and with an invalid
> CURLOPT_CAINFO I don't give any (from curl's point of view)...
> (I will have a look at the source, maybe that clears things up a bit)

It did :-)

I need to set both CURLOPT_CAINFO and CURLOPT_CAPATH to NULL, then curl
won't try to read any files...
Now I get an access violation in my sslctx callback... but that might
not be related at all.

Sebastian
Received on 2006-03-02