--On 12 January 2011 11:07:56 +0100 Gabriel Petrovay
<gabriel.petrovay_at_28msec.com> wrote:

> Is this a bug, feature or "by design"? If the letter two, why? Where
> does curl pick the certificates on Windows from (that is different
> from other platforms)?

As in the text you quoted:

> curl performs SSL certificate verification by default, using a "bundle"
>  of Certificate Authority (CA) public keys (CA certs). The default
>  bundle is named curl-ca-bundle.crt; you can specify an alternate file
>  using the --cacert option.
> If this HTTPS server uses a certificate signed by a CA represented in
>  the bundle, the certificate verification probably failed due to a
>  problem with the certificate (it might be expired, or the name might
>  not match the domain name in the URL).

So, you know the certificate doesn't have a problem as it works on
Windows. This would tend to indicate the CA Cert bundle on your
windows platform includes the CA's certificate, but the CA Cert
bundle on Linux doesn't. This can normally be fixed by installing
a package of up to date CA certificates. Note these aren't part
of curl but part of your distribution.

-- 
Alex Bligh
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html