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
This is a proposal for a certificate chain validation tool for device vendors generating certificate chains that follow DMTF / TCG / OCP Security specifications. In this context "standalone" means that the certificate chain itself is the primary input to the tool. The tool would perform standard certificate chain checks. In addition it would also check
for the presence of mandatory OIDs and fields
for the absence of forbidden OIDs and fields
that the certificate chain is encoded correctly
against the relevant DMTF / TCG / OCP Security specifications. The specifications of interest include
Activity
alistair23 commentedon Dec 16, 2025
SPDM-Utils has support for this, it's not standalone, but it shouldn't be too hard to make it standalone
steven-bellock commentedon Dec 16, 2025
Does
x509_parserhave strict DER checking? Ie, it would flag something like DMTF/libspdm#3419 if it was improperly DER-encoded?alistair23 commentedon Dec 17, 2025
Ah, that's interesting.
We wouldn't catch that, we leave SPDM spec checks to libspdm and are only checking "TCG DICE Concise Evidence Binding for SPDM" compliance.
x509_parserdoesn't seem to have strict checking, but we could implement a validator to check things like that.steven-bellock commentedon Feb 4, 2026
chipsalliance/caliptra-dpe#513 provides additional motivation.
bluegate010 commentedon Feb 24, 2026
+1 to using an existing foundation if one is nearly there.