You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 93d1f5d
Browse filesBrowse the repository at this point in the historyBrowse files
tools: generate distrust-after dates from certdata.txt
Mozilla's CKA_NSS_SERVER_DISTRUST_AFTER dates are enforced by the
distrust-after table in src/crypto/crypto_context.cc, which so far had to
be typed by hand: find the root in certdata.txt, hash its public key,
convert the date to an epoch. The emSign G1 entry was first written with
the wrong year, which is the kind of slip a generator avoids.
Add tools/mk-root-certs-distrust.mjs, which reads tools/certdata.txt and
src/node_root_certs.h and writes src/node_root_certs_distrust.h with one
entry per bundled root that carries a distrust-after date. The verify
callback includes that header as kDistrustAfterBundled and keeps the
hand-written table for dates Mozilla publishes between NSS releases and
for the test fixture. update-root-certs.mjs runs the generator after
mk-ca-bundle.pl and reports date changes in the commit message it
produces, so the weekly root-certificates job picks new dates up with
no extra step. A test regenerates the header and fails when the
committed copy is out of date with certdata.txt.
With the current certdata.txt snapshot the generated table holds
Izenpe.com only; emSign Root CA - G1 and Firmaprofesional stay in the
hand-written table until the next root certificate update brings their
dates in.
Refs: #67391
Assisted-by: Claude, Codex, Mistral
Signed-off-by: Ulises Gascon <ulisesgascongonzalez@gmail.com>
0 commit comments