Allow Responder Integrator to specify additional opaque data#3485
Open
Allow Responder Integrator to specify additional opaque data#3485
Conversation
Member
|
@steven-bellock would you please review? |
| * opaque_data buffer. | ||
| * | ||
| * @retval true OpaqueData field is generated successfully. | ||
| * If return true, responder will not generate any opaque data, |
Contributor
There was a problem hiding this comment.
If the Integrator provides the opaque data then they must also set the secured_message_version in the session_info, correct?
Contributor
Author
There was a problem hiding this comment.
Yes, that is correct.
Contributor
There was a problem hiding this comment.
libspdm_set_data currently does not support LIBSPDM_DATA_SESSION_SECURED_MESSAGE_VERSION, so that would need to be expanded.
fix DMTF#3401 Signed-off-by: Aaron Li <aaron.li@intel.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix #3401