Fix KEY_PAIR_INFO PQC length cursor handling#3607
Open
Conversation
2729807 to
198c9be
Compare
Signed-off-by: Cezary Zwolak <cezary.zwolak@intel.com>
625b0f6 to
5f479cc
Compare
KEY_PAIR_INFO PQC length cursor handling
jyao1
approved these changes
Apr 23, 2026
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
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 #3593.
Use raw PQC length fields for cursor advancement and copy only min(raw_len, 4) into local 32-bit values.
Add requester unit test coverage for SPDM 1.4 oversized PQC capability length parsing regression.
Align KEY_PAIR_INFO requester test fixtures with mixed classical/PQC validation rules.