Re: Firefox 2.0.0.5 handling of binary files
- From: Chris Ridd <chrisridd@xxxxxxx>
- Date: Mon, 30 Jul 2007 22:12:36 +0100
On 2007-07-30 21:53:43 +0100, Clive <c_barrows@xxxxxxxxxxx> said:
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).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
I must still be doing something wrong here, as the I don't get any
message about the certificate expiring when I just download log files.
SSL (which is what HTTPS uses) is a security mechanism that involves something called X.509. Essentially X.509 is a way of saying that company A has shown itself trustworthy to company B (usually involving payment :-), and can prove this by showing you a mathematically unforgeable certificate. (And potentially company B could have proved itself trustworthy to company C, etc etc) In X.509 lingo, company B is acting as a certificate authority, or CA.
Now the question is do *you* trust company B to verify company A?
Most web browsers (and OSes) ship with a bunch of certificates from companies like B, and are configured to automatically trust these companies to verify web servers. OS X contains a special keychain with all of these certificates in, and Safari uses that. Firefox doesn't use OS X's keychain, and instead has its own built-in list of trusted certificates.
So Safari/Firefox are probably configured to trust whichever company it was that signed your web server's certificate, and curl it seems has not been configured that way.
If you pretend to curl that you do trust the certificate (or don't want it to check) then you should get the info you desire. Just do what curl's error message said, and type:
curl -k -I https://....
I'm concerned that I'm taking up too much of everyone's time here -
but still very appreciative.
No problem.
Cheers,
Chris
.
- Follow-Ups:
- Re: Firefox 2.0.0.5 handling of binary files
- From: Clive
- Re: Firefox 2.0.0.5 handling of binary files
- References:
- Firefox 2.0.0.5 handling of binary files
- From: Clive
- Re: Firefox 2.0.0.5 handling of binary files
- From: Sander Tekelenburg
- Re: Firefox 2.0.0.5 handling of binary files
- From: Clive
- Re: Firefox 2.0.0.5 handling of binary files
- From: Richard Maine
- Re: Firefox 2.0.0.5 handling of binary files
- From: Clive
- Re: Firefox 2.0.0.5 handling of binary files
- From: Jolly Roger
- Re: Firefox 2.0.0.5 handling of binary files
- From: Clive
- Re: Firefox 2.0.0.5 handling of binary files
- From: Chris Ridd
- Re: Firefox 2.0.0.5 handling of binary files
- From: Clive
- Re: Firefox 2.0.0.5 handling of binary files
- From: Jolly Roger
- Re: Firefox 2.0.0.5 handling of binary files
- From: Clive
- Firefox 2.0.0.5 handling of binary files
- Prev by Date: Re: Dragging to documents
- Next by Date: Re: Meta information from iCal entry
- Previous by thread: Re: Firefox 2.0.0.5 handling of binary files
- Next by thread: Re: Firefox 2.0.0.5 handling of binary files
- Index(es):
Relevant Pages
|