Re: Firefox 2.0.0.5 handling of binary files

On Jul 30, 9:35 pm, Jolly Roger <wbyyleb...@xxxxxxxxx> wrote:
On 2007-07-30 15:01:30 -0500, Clive <c_barr...@xxxxxxxxxxx> said:

Thanks, Roger, but that is exactly what I did do. When I tried your
example, it worked immediately, and I received dozens of lines, ending
with:
-4/--ipv4 Resolve name to IPv4 address
-6/--ipv6 Resolve name to IPv6 address
-#/--progress-bar Display transfer progress as a progress bar

and

--data-ascii <data> HTTP POST ASCII data (H)
--data-binary <data> HTTP POST binary data (H)

Those are lines of help from the curl help page.

Curl will display the help page whenever you type a command it does not
understand. This leads me to believe you did not type the command
*exactly* as I gave it to you.

Are you manually typing the command rather than copying and pasting??
Try it again, but make sure you put a space between -i and the URL as
shown here:

curl -ihttp://jollyroger.kicks-ass.org/jollyroger/test.txt

Ah-ha, so I didn't get what I thought was the right information.

I've manually typed the curl line and also copied and pasted, both
with the same result - also with & without the space before the 'I'.

Doing it as you suggested with curl -u "username:password" -I https://.....
(changing username:password for the real ones!), I now get:
curl: (60) SSL certificate problem, verify that the CA cert is OK.
Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
verify failed
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). 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.

I'm concerned that I'm taking up too much of everyone's time here -
but still very appreciative.
Clive

.

Relevant Pages

  • Need pointers on managing client certs...
    ... I've been exploring openssl and curl, ... client side which appears to be subject to periodic expiration. ... get things to work simply by just telling curl not to do certificate ... so to get their cert file manually updated. ...
    (comp.security.unix)
  • [ GLSA 200909-20 ] cURL: Certificate validation error
    ... An error in the X.509 certificate handling of cURL might enable remote ... attackers to conduct man-in-the-middle attacks. ... Security is a primary focus of Gentoo Linux and ensuring the ...
    (Bugtraq)
  • [Full-disclosure] [ GLSA 200909-20 ] cURL: Certificate validation error
    ... An error in the X.509 certificate handling of cURL might enable remote ... attackers to conduct man-in-the-middle attacks. ... Security is a primary focus of Gentoo Linux and ensuring the ...
    (Full-Disclosure)
  • Re: Need pointers on managing client certs...
    ... I've been exploring openssl and curl, ... > client side which appears to be subject to periodic expiration. ... > get things to work simply by just telling curl not to do certificate ... OCSP is built into later versions of openssl. ...
    (comp.security.unix)