Skip to content

Conversation

@joshua-spacetime
Copy link
Collaborator

@joshua-spacetime joshua-spacetime commented Feb 10, 2026

Description of Changes

Blocks procedures from requesting private ip ranges after dns resolution.

API and ABI breaking changes

None

Expected complexity level and risk

  1. I may have missed a range.

Testing

  • Unit tests for IP address matching
  • Smoketest for blocking a private IP address

Copy link
Collaborator

@bfops bfops left a 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)

Copy link
Contributor

@Kasama Kasama left a 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

@joshua-spacetime joshua-spacetime force-pushed the joshua/block-internal-ips branch from e5a1772 to 7acdc5a Compare February 10, 2026 16:57
Copy link
Contributor

@Kasama Kasama left a 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!

@Kasama
Copy link
Contributor

Kasama commented Feb 10, 2026

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants