Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: Caml List <caml-list@inria.fr>
Subject: RE: [Caml-list] ocaml.org ssl certificate problem
Date: Tue, 30 Sep 2014 07:31:59 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9E95BFDA2@Remus.metastack.local> (raw)
In-Reply-To: <CAKR7PS-TFC8JkCJtG=mv3p=UNaX5xmSe2YMfdm+eGT-Ut+dNgg@mail.gmail.com>

Milan Stanojevic wrote:
> Firefox is complaining about ocaml.org's certificate issuer, says "unknown
> issuer".
> Chromium doesn't complain and allows me to open ocaml.org.
> 
> It's possible my configuration is messed up.
> Anyone else having this problem?

It looks like ocaml.org's SSL is not correctly configured and it's not sending the intermediate CA certificate (see output of http://www.ssltool.com/?action=sslCheckOpenSSL&address=ocaml.org). The intermediate CA certificate is at http://wiki.gandi.net/en/ssl/intermediate, by the look of it.

This will be a problem viewing in an evangelical browser like Firefox which doesn't include a stash of common intermediate CA certificates, but not so much of a problem in Chromium (especially if you do happen to be running on Windows, where it uses Microsoft's built-in certificate store) which is a little more liberal - or less liberal, depending on political viewpoint! - about the certificates it pre-installs for you!

However, it will have problems in Chromium later this year when SHA1 starts to be retired: http://googleonlinesecurity.blogspot.co.uk/2014/09/gradually-sunsetting-sha-1.html


David

      parent reply	other threads:[~2014-09-30  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30  2:15 Milan Stanojević
2014-09-30  2:28 ` Peter Zotov
2014-09-30  7:31 ` David Allsopp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E51C5B015DBD1348A1D85763337FB6D9E95BFDA2@Remus.metastack.local \
    --to=dra-news@metastack.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox