docs: the network mediation design — reachability, per-execution policy, and the SNI guard - #1
Merged
Merged
Conversation
…sign Number the twelve design decisions and index them, so each choice can be cited on its own: the per-backend reachability routes, the in-house relay, the refusal to restore ambient network, the SNI guard, the per-execution instance and its rejected alternative, method restriction and the two-phase network profiles. Add self-contained implementation phases, each shippable and testable without the ones after it, plus the open questions that should not be closed by implementation alone. Cite the prior art by name with links and verified quotations. Correct the Codex characterisation: a filtering proxy now exists behind features.network_proxy but ships off by default, so the default remains boolean rather than there being no proxy at all. Add the Seatbelt and bubblewrap topology diagrams, the seven-step tunnel attack trace and the guard state machine. Soften the domain-fronting claim to what is actually attributable to the CDNs. Wrap to the 79-column convention used by the other documents.
davidb987654
changed the title
davidb987654
marked this pull request as ready for review
August 23, 2026 18:54
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.
Design-only document (no code) specifying the network mediation that a confined
workload relies on: how it reaches the Netd proxy — and nothing else — across
sandbox backends, and how a guard on the cleartext TLS ClientHello closes the
destination-identity gap that the sealed allowlist alone cannot.
The document builds on the shipped surface (exact allowlist, pinned DNS,
CONNECT/forward/SOCKS5, policy digest, receipts, TLS provider seam,
maelys_netd_profile) and references those docs rather than restating them.Contents:
Bubblewrap (empty
--unshare-netstack reached via a bind-mounted Unix socketplus an in-house in-namespace relay, never socat), the golden rule, and the
inherited
SCM_RIGHTSfd route for Maelys-aware workloads.opaque tunnel leaves, why the SNI is cleartext by necessity, the guard itself,
and why tunnel and TLS are successive rather than nested.
execution, profile-authorized environment augmentation, the digest chain, and
method-restriction / two-phase network as policy choices.
Status: design, targeting netd 0.2 (reachability, per-execution auth) and 0.3
(SNI guard). No code. Do not merge without owner review.