Skip to content
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

Update test case 2 (Capabilities) to support SPDM 1.3 #146

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

wmaroneAMD
Copy link
Contributor

This updates test case 2 to check for and confirm report of SPDM 1.3 in GET_CAPABILITIES. All tests are the same at this time, and the test body for 1.2 has been made common with checks to toggle support for 1.3.

This does not validate any new capabilities, such as the supported algorithms block, added in SPDM 1.3.

@wmaroneAMD
Copy link
Contributor Author

Other than the supported algorithms block, I'm not seeing anything immediately obvious that is new. Mostly just things that will trigger new checks in later tests.

@wmaroneAMD
Copy link
Contributor Author

Hmm also need to update the docs.

@wmaroneAMD
Copy link
Contributor Author

Since this results in 2.5 and 2.7 being basically identical, would it make more sense to change 2.5 to 1.2+ and have a specific test for anything only in 1.3?

This updates test case 2 to check for and confirm report
of SPDM 1.3 in GET_CAPABILITIES. All tests are the same
at this time, and the test body for 1.2 has been made common
with checks to toggle support for 1.3.

This does not validate any new capabilities, such as the supported
algorithms block, added in SPDM 1.3.

Signed-off-by: Will Marone <[email protected]>
@jyao1
Copy link
Member

jyao1 commented Jan 15, 2025

If they are identical, we can just use 1.2+.

@wmaroneAMD
Copy link
Contributor Author

Ok. I will unify the general case and create a specific test for the 1.3 feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants