-
Notifications
You must be signed in to change notification settings - Fork 686
Block procedures from requesting private ip ranges #4243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tools/ci changes LGTM! (I didn't review anything else)
Kasama
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops. Accidentally approved instead of requesting changes.
Again, we probably don't want to test this many IPs in the final test, but I've commented with them for now so we can be pretty sure those ranges are covered
e5a1772 to
7acdc5a
Compare
Kasama
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All ranges look to be covered!
|
just one nit. As these ip checks are a big blob of numbers and checks kinda unrelated to the rest of the file. Would it make sense to move those checks onto a separate module instead? |
Description of Changes
Blocks procedures from requesting private ip ranges after dns resolution.
API and ABI breaking changes
None
Expected complexity level and risk
Testing