Strengthen parsePath and drop two temporary assumptions related to SCION issues
#364
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
Dspil
approved these changes
Jul 9, 2024
matzf
pushed a commit
to scionproto/scion
that referenced
this pull request
Jul 11, 2024
This PR strengthens the checks performed by the `parsePath` method to address the issues #4524 and #4531. In particular, I added two checks: - We check that the `CurrHF` field of the parsed path is compatible with the `CurrINF` field - We check that non-peering segments have at least two hops The proof that solution is correct is available in viperproject/VerifiedSCION#364
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.
Based on scionproto/scion#4556