-
Notifications
You must be signed in to change notification settings - Fork 14
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
Version.InvalidRequest test expectations are inaccurate #124
Comments
was added in the 1.2 specification and was not backported to 1.0/1.1. For the most part we can just remove this check since the Requester would have a bug and it probably wouldn't care if the response message is correct or not. |
I'll ask the SPDM WG if the above text should be back-ported to the 1.0/1.1 specifications. |
oh, you're right! did not notice this in the specification. |
@jyao1 to remove the test. I'll file an issue with the SPDM Working Group to bring visibility. |
Fix: DMTF#124 Signed-off-by: Jiewen Yao <[email protected]>
Ref: DMTF/SPDM-Responder-Validator#124 Signed-off-by: Jiewen Yao <[email protected]>
Fix: #124 Signed-off-by: Jiewen Yao <[email protected]>
Ref: DMTF/SPDM-Responder-Validator#124 Signed-off-by: Jiewen Yao <[email protected]>
We have stumbled upon this while running SPDM-Reponder-Validator tests standalone, without the spdm-emu infra.
The current test case is:
Assertion 1.2.3 is inaccurate - this is only guaranteed to happen if this happens pre-VCA (or post-successful GET_VERSION). Post-VCA this error can return the negotiated SPDM version.
The text was updated successfully, but these errors were encountered: