Work around broken VICALs and RICALs.#1807
Merged
Merged
Conversation
For VICALs and RICALs according to ISO 18013-5 the SKI (Subject Key Identifier) is present in both `CertificateInfo` / `RICALCertificateInfo` CBOR and the X.509 certificate itself. Our parsers use the CBOR value which is less than ideal for VICALs and RICALs that encode this field incorrectly. Instead, use the value from the certificate and log a warning if the two SKIs differ. Fixes #1806. Test: Manually tested and unit tests. Signed-off-by: David Zeuthen <zeuthen@google.com>
davidz25
changed the title
sorotokin
approved these changes
Jul 10, 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
2 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.
For VICALs and RICALs according to ISO 18013-5 the SKI (Subject Key Identifier) is present in both
CertificateInfo/RICALCertificateInfoCBOR and the X.509 certificate itself. Our parsers use the CBOR value which is less than ideal for VICALs and RICALs that encode this field incorrectly. Instead, use the value from the certificate and log a warning if the two SKIs differ.Fixes #1806.