fix: bundle GlobalSign Root R46 and R3 as MDS trust anchors instead of downloading one #13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/mds-root-certificate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
mds/globalsign-root-r46.crt,mds/globalsign-root-r3.crt) as trust anchors for the FIDO MDS blob signature.webauthn.mds.root-cert-url, plain http) and its cache fileroot-cert.pem.webauthn.mds.root-cert-pathto replace the bundled certificates (DER or PEM, may contain several). A configured but unusable file fails the startup; it never falls back silently.Why
http://on first start: it was only as trustworthy as that connection, and a missing network broke the bean creation.Tests
MdsRootCertificatesTest(13 tests): pins the SHA-256 fingerprints of both bundled certificates; DER, PEM and multi-certificate override; a missing, garbage or empty override fails (no silent fallback); expired and not-yet-valid anchors are skipped with a warning; fails if none is valid.PasskeyMDSAuth(MDS is mocked in the integration test).Notes
webauthn.mds.root-cert-urlis removed. Stalemds-cache/root-cert.pemfiles can be deleted.mds/*.crtmust be registered for the native build.