[TOB] DEV-3784: ID-5 #20
Open
Conversation
This file contains 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
| X509CertObj memory issuer; | ||
| bytes memory crl; |
Check warning
Code scanning / Slither
Uninitialized local variables Medium
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.
See automata-network/automata-on-chain-pccs#22 for more details about
authorityKeyIdentifierandsubjectKeyIdentifierfields introduced to theX509HelperandX509CRLHelperlibraries.This PR introduces two changes:
authorityKeyIdentifiervalue of the CRL must match with thesubjectKeyIdentifiervalue of the CA Issuer. This is cheaper than performing ECDSA verification (assuming not using RIP-7212).authorityKeyIdentifiervalue of a subject certificate must match with thesubjectKeyIdentifiervalue of the CA issuer before performing ECDSA verification.ID-5 also raises issues regarding CRL expiration check, which is being resolved in #19.