fix: deny ranges take precedence over allow ranges - #296
Open
AruneshDwivedi wants to merge 1 commit into
Open
Conversation
classifyAddr checked AllowRanges before DenyRanges, so an address explicitly denied via --deny-address (or --deny-range) was still allowed when it also fell inside an --allow-range. Check DenyRanges first so a denied address is always rejected regardless of any allow range. Fixes stripe#236 Signed-off-by: Arunesh Dwivedi <[email protected]>
|
|
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
1 participant
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.
classifyAddr evaluated AllowRanges before DenyRanges, so an address denied by --deny-address (appended to DenyRanges) was still allowed whenever it also matched an --allow-range. The order is swapped so a denied address is always rejected. Extended TestSelectTargetAddr with cases where an allow range overlaps a denied address.