boulder/test/hierarchy
Aaron Gable 99035226d8
Add name and key hashes to issuance.Certificate (#5812)
These hashes are useful for OCSP computations, as they are the two
values that are used to uniquely identify the issuer of the given cert in
an OCSP request. Here, they are restricted to SHA1 only, as Boulder
only supports SHA1 for OCSP, as per RFC 5019.

In addition, because the `ID`, `NameID`, `NameHash`, and `KeyHash`
are relatively expensive to compute, introduce a new constructor for
`issuance.Certificate` that computes all four values at startup time and
then simply returns the precomputed values when asked.
2021-12-01 12:11:10 -08:00
..
README.md Add name and key hashes to issuance.Certificate (#5812) 2021-12-01 12:11:10 -08:00
ee-e1.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
ee-e1.key.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
ee-e2.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
ee-e2.key.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
ee-r3.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
ee-r3.key.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
ee-r4.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
ee-r4.key.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-e1.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-e1.key.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-e2.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-e2.key.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-r3-cross.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-r3.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-r3.key.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-r4-cross.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-r4.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
int-r4.key.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
root-dst.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
root-x1-cross.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
root-x1.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
root-x2-cross.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00
root-x2.cert.pem wfe2: Check signatures before serving cert chains (#5273) 2021-02-09 09:09:49 -08:00

README.md

Boulder Test Hierarchy

This directory contains certificates which are analogues of Let's Encrypt's active hierarchy. These are useful for ensuring that our tests cover all of our actual situations, such as cross-signed intermediates, cross-signed roots, both RSA and ECDSA roots and intermediates, and having issuance chains with more than one intermediate in them. Also included are a selection of fake end-entity certificates, issued from each of the intermediates. This directory does not include private keys for the roots, as Boulder should never perform any operations which require access to root private keys.

Usage

These certificates (particularly their subject info and public key info) are subject to change at any time. Values derived from these certificates, such as their Serial, IssuerID, Fingerprint, or IssuerNameID should never be hard-coded in tests or mocks. If you need to assert facts about those values in a test, load the cert from disk and compute those values dynamically.

In general, loading and using one of these certificates for a test might look like:

ee, _ := CA.IssuePrecertificate(...)
cert, _ := issuance.LoadCertificate("test/hierarchy/int-e1.cert.pem")
test.AssertEqual(t, issuance.GetIssuerNameID(ee), issuer.NameID())