Context
The Opus review of wolftpm-core found that the GET_CERTIFICATE fetch loop and wolfSPDM_ConnectStandard are exercised only by the spdm-emu CI job. ParseCertificate, ParseDigests and chain validation have unit tests, but the loopback peer in test_peer_dispatch does not answer GET_VERSION, CAPABILITIES, ALGORITHMS, DIGESTS or CERTIFICATE.
Origin
main...wolftpm-core
What is needed
- Extend the loopback peer to serve GET_DIGESTS and GET_CERTIFICATE from
test_rsp_chain_der in small portions.
- Cases: a multi-portion chain, a zero-length non-final portion, a chain-header Length mismatch, and a responder DataTransferSize below 1032 that forces
reqLen clamping.
- Run
wolfSPDM_ConnectStandard end to end over the loopback: slot selection, ValidateCertChain, KEY_EXCHANGE and FINISH.
Blockers and dependencies
No response
Acceptance criteria
make check covers each branch of wolfSPDM_GetCertificate and a full wolfSPDM_ConnectStandard without spdm-emu.
Context
The Opus review of
wolftpm-corefound that the GET_CERTIFICATE fetch loop andwolfSPDM_ConnectStandardare exercised only by the spdm-emu CI job.ParseCertificate,ParseDigestsand chain validation have unit tests, but the loopback peer intest_peer_dispatchdoes not answer GET_VERSION, CAPABILITIES, ALGORITHMS, DIGESTS or CERTIFICATE.Origin
main...wolftpm-core
What is needed
test_rsp_chain_derin small portions.reqLenclamping.wolfSPDM_ConnectStandardend to end over the loopback: slot selection, ValidateCertChain, KEY_EXCHANGE and FINISH.Blockers and dependencies
No response
Acceptance criteria
make checkcovers each branch ofwolfSPDM_GetCertificateand a fullwolfSPDM_ConnectStandardwithout spdm-emu.