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
I ran the spdm_responder_validator test case 7.1 with below Responder settings:
Requester
SPDM (as the setup function)
DATA_TRANSFER_SIZE = 256
MAX_SPDM_MSG_SIZE = 0x1200 (this is conflict with DATA_TRANSFER_SIZE)
Responder
SPDM 1.3
DATA_TRANSFER_SIZE = 256
MAX_SPDM_MSG_SIZE = 0x1200
CHUNK_CAP = 1
The libspdm_get_response_capabilities seems cannot detect the conflict while handling get capability.
How should the responder handle this?
The text was updated successfully, but these errors were encountered:
owen126315
changed the title
Questions for capability agreement between SPDM requester and responder
spdm_responder_lib cannot identify capability conflict for DATA_TRANSFER_SIZE and MAX_SPDM_MSG_SIZE for SPDM version 1.0 & 1.1
Jan 23, 2024
What SPDM version(s) does the Requester support? If it's the https://github.com/DMTF/SPDM-Responder-Validator then it cannot talk to a 1.3-only Responder since we haven't updated Responder Validator to 1.3 yet.
owen126315
changed the title
spdm_responder_lib cannot identify capability conflict for DATA_TRANSFER_SIZE and MAX_SPDM_MSG_SIZE for SPDM version 1.0 & 1.1
spdm_responder_lib cannot identify capability conflict of DATA_TRANSFER_SIZE and MAX_SPDM_MSG_SIZE for SPDM version 1.0 & 1.1
Jan 24, 2024
I guess the root cause is can both requester and responder support chunk, not SPDM version. the DATA_TRANSFER_SIZE and MAX_SPDM_MSG_SIZE must be equal if chunk is not support.
And libspdm_get_response_capabilities never check these two parameters when request.version = 1.0.
I ran the spdm_responder_validator test case 7.1 with below Responder settings:
Requester
Responder
The libspdm_get_response_capabilities seems cannot detect the conflict while handling get capability.
How should the responder handle this?
The text was updated successfully, but these errors were encountered: