Open
Bug 1940903
Opened 1 year ago
Updated 15 days ago
Replace hard-coded SHA256 root hashes by full certificates
Categories
(Application Services :: Remote Settings, enhancement)
Application Services
Remote Settings
Tracking
(Not tracked)
NEW
People
(Reporter: leplatrem, Unassigned)
Details
In https://github.com/mozilla/application-services/pull/6534 we introduced signature verification in the RS client.
Since rc_crypto/pkixc require the SHA256 hash of the root certificate, we hardcoded the values for our PROD and NONPROD instances.
Instead of this, we should ship the root certificate content, and compute hashes at build time.
This would have the following benefits (quoted from Dana and Jeff on Slack):
- align with desktop and make it easy to check if the roots are the same as in mozilla-central
- in urgent cases, sign information from certificates with the same key material but different metadata without breaking old clients that can't get the new version of the certificate
- make it easier to add accepted root pool since most x509-using libraries have that as an abstraction. With root hashes, that code has to be written by hand. So when you invariably need to add more roots, you usually only need to update configs, not code.
CC Johannes as he is doing some work with rc_crypto which may overlap here.
| Reporter | ||
Comment 2•18 days ago
|
||
Johannes, do you have more info about the status of this work?
Thank you :)
Flags: needinfo?(joschmidt)
Comment 3•15 days ago
|
||
Oh, I think all my work on rc_crypto is complete so far.
Flags: needinfo?(joschmidt)
You need to log in
before you can comment on or make changes to this bug.
Description
•