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

spdm_version: add version select support #11

Merged
merged 1 commit into from
Nov 3, 2023

Conversation

twilfredo
Copy link
Collaborator

@twilfredo twilfredo commented Nov 3, 2023

This allows us to select the spdm data message version used by the libspdm responder. The default (as before) is version 1.3. We can now select versions 1.0..=1.3.

This is sub-argument to the response command, usage as below:

$ spdm_utils --qemu-server response --spdm-ver 1.3

Tested by running get-version request on a responder with version 1.0, 1.1, 1.2, 1.3. Note that, 1.0 fails on key-exchange, likely due to mismatched secure version. Will investigate.

This allows us to select the spdm data message version used by the
libspdm responder. The default (as before) is version 1.3. We can now
select versions 1.0..=1.3.

This is sub-argument to the response command, usage as below:

```
$ spdm_utils --qemu-server response --spdm-ver 1.3
```

Signed-off-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
@twilfredo twilfredo changed the title libspm: add version select support spdm_version: add version select support Nov 3, 2023
@twilfredo
Copy link
Collaborator Author

twilfredo commented Nov 3, 2023

Note: 1.3 is implicitly selected by libspdm when version is unspecified but is also has some kinks to work out, i.e: DMTF/libspdm#2282 (comment)

@alistair23 alistair23 merged commit 0a417f8 into master Nov 3, 2023
@alistair23 alistair23 deleted the wilfred/add-spdm-version-support branch November 3, 2023 04:36
@l1k
Copy link

l1k commented Nov 4, 2023

1.0 fails on key-exchange

I think that's expected given KEY_EXCHANGE was added to spec version 1.1.0.

@twilfredo
Copy link
Collaborator Author

1.0 fails on key-exchange

I think that's expected given KEY_EXCHANGE was added to spec version 1.1.0.

Yep, that was the case.

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.

3 participants