On Mon, Jul 23, 2012 at 11:52:31PM -0700, usama yaseen wrote:
> yes previously ssl support was not enabled and https was not included in the
> protocols supported, i installed SSL from source and now my configure option is
> like this:
>
> ./configure --host=arm-none-linux-gnueabi --build=i686-linux CFLAGS='-Os'
> --enable-smtp --with-ssl
>
> after installing curl, when i type curl-config --protocols in the terminal,
> https is included in the list of supported protocols.

But what does curl --version say? That's the more reliable indicator
since it takes the run-time linking into account, which curl-config does
not.

> But even after all this the output of sample application is the same,

Exactly the same?

> When i try to open any site with the curl, i got this which is surely related
> to the certificate:
> root@am180x-evm:/home# curl https://www.gmail.com
> curl: (60) SSL certificate problem: certificate is not yet valid
> More details here: http://curl.haxx.se/docs/sslcerts.html
>
> curl performs SSL certificate verification by default, using a "bundle"
> of Certificate Authority (CA) public keys (CA certs). If the default
> bundle file isn't adequate, 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).
> If you'd like to turn off curl's verification of the certificate, use
> the -k (or --insecure) option.
>
> Now how can i resolve this ? should i specify the certificate in while
> configuring ? and from where do i get the certificate of arm ? or will it be
> the same as of pc ?

See http://curl.haxx.se/docs/sslcerts.html

>>> Dan
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-07-24