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
No session required in hanshake in the clear.
But it returns SessionRequired if the requester sends FINISH in session in handshake in the clear.
I think InvalidRequest or UnexpectedRequest would be appropriate.
I guess one of the questions is why is libspdm decrypting anything at all if the session state is still in the handshake phase and HANDSHAKE_IN_THE_CLEAR_CAP is set for both endpoints.
And going even further why do the Request-direction and Responder-direction handshake secrets even exist if HANDSHAKE_IN_THE_CLEAR_CAP is set for both endpoints? Filed https://github.com/DMTF/SPDM-WG/issues/3684 to make that more explicit in the specification.
No session required in hanshake in the clear.
But it returns
SessionRequired
if the requester sendsFINISH
in session in handshake in the clear.I think
InvalidRequest
orUnexpectedRequest
would be appropriate.libspdm/library/spdm_responder_lib/libspdm_rsp_finish.c
Lines 430 to 434 in 238fb80
The text was updated successfully, but these errors were encountered: