fix(auth): reject scoped capability re-rooting#189
Open
marcus-pousette wants to merge 1 commit into
Open
Conversation
da5ddf4 to
bff75b8
Compare
8e0d3c0 to
a60fc61
Compare
db233a2 to
d3f633a
Compare
a60fc61 to
93b6c16
Compare
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.
Problem
A delegated capability was allowed to choose a different subtree root when the receiver's current ancestry said it was a descendant of the proof root. That ancestry can change as operations arrive, so different peers could disagree about whether the delegation was valid.
What changes
maxDepth, or add exclusions.Fast paths
Tests
Stack
Stacked on #188.