401855 - Need SSL certificate for caminobrowser.org

Status: VERIFIED FIXED

(Camino Graveyard :: Product Site, enhancement)

Description

[Samuel Sidler (old account; do not CC)]

As part of our update system, we want to check an https URI when checking for updates. I've emailed our host to start getting that setup. This bug is to track that progress.

Stuart, a couple of questions:
  1. Are we going to verify the cert is valid when checking for updates? Or are
     we just verifying that it's the https link? (I'm assuming you thought of
     this, but it came to mind.)
  2. Where do we want the file to live? Should it be on a subdomain
     (update.cb.o) or a top-level directory (cb.o/update) or... ?

I'm making this bug block 1.6b1 since we need to have it in place by then to test.

Comment 1

[Stuart Morgan]

(In reply to comment #0)
> 1. Are we going to verify the cert is valid when checking for updates? Or are
>    we just verifying that it's the https link?

I'm not sure what you are asking. The update URL will be an https URL, so either the cert will be valid, or the connection will fail.

> 2. Where do we want the file to live? Should it be on a subdomain
>    (update.cb.o) or a top-level directory (cb.o/update) or... ?

Doesn't matter to me, but we need to decide that right now, so we can ship a1 with the correct URL.

Comment 2

[Samuel Sidler (old account; do not CC)]

Per the meeting today, we're going to use https://caminobrowser.org/update/. I've emailed our host with this information.

Comment 3

[Samuel Sidler (old account; do not CC)]

We'll be getting a 2-year 256-bit certificate for caminobrowser.org. I'll update this bug when everything is setup.

Comment 4

[Samuel Sidler (old account; do not CC)]

This has been setup. From our host: "This is a RapidSSL 256 bit certificate extended for 2 years."

Closing.