Repository navigation
Proposal: start sandboxes with a closed network by default #651
sumansaurabh
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The problem
A sandbox with no network policy can reach the internet, plus anything its server can reach. That includes private addresses, the cloud metadata service (
169.254.169.254) and other sandboxes. V8 isolates are the one exception. The server-wide guards only apply once the operator writes a network policy file: a default policy, address ranges that are always blocked, and a guard for AerolVM's own ports. A fresh install has no such file.What you can do today
Set
networkBlockAllornetworkAllowOuton every create. Or write a policy file (SB_EGRESS_OPERATOR_FILE) withdefault_policy: block_all, add169.254.169.254/32todeny_cidrs, and keep the control-port guard on. The file looks like this:A starting shape
Two steps, so nobody's setup breaks without warning:
install.shwrites a policy file withdefault_policy: block_all. Existing servers keep their behavior until the operator opts in, and a release note says how.A sandbox that needs the internet still asks for it with
networkAllowOut.Questions for you
block_all, or with an allow list of common package sites?How to weigh in
React with 👍 if you need this, and comment with your answers.
Want to talk it through? Book a call with the maintainer, or join the community call on the first Saturday of every month at 8 pm Pacific Time.
If your company needs this soon, you can sponsor the work. It is built in the open and ships to everyone.
All reactions