-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SET_CERT: ResetRequired handling #2864
Comments
Not that I know of.
There can be, if it is needed. I think in a pull request I commented that libspdm needs to check with the Integrator before sending libspdm/include/hal/library/responder/csrlib.h Lines 23 to 26 in 5149b56
SET_CERTIFICATE . In particular libspdm blindly sends ResetRequired if the Responder's CERT_INSTALL_RESET_CAP is set : libspdm/library/spdm_responder_lib/libspdm_rsp_set_certificate.c Lines 302 to 309 in 5149b56
libspdm_write_certificate_to_nvm can return whether errors are required to libspdm. For the Busy response to GET_CERTIFICATE we just need a per-slot way for the Integrator to communicate the state of the certificate slot in the spdm_context .
|
It seems that the following behaviors haven't been implemented in libspdm yet.
If that's the case, is there any existing issue or plan to fix it?
"If the device temporarily cannot write to a slot, including in a case when it receives overlapping SET_CERTIFICATE requests from different Requesters, then the device shall respond with anErrorCode=Busy response.
When a reset is required for a pending previous SET_CERTIFICATE request and the device receives a GET_CERTIFICATE request for a pending slot or a GET_DIGESTS request, the device shall respond with an ErrorCode=ResetRequired response."
The text was updated successfully, but these errors were encountered: