enforce enclave ingress and egress allowlists #457
No reviewers
Labels
No labels
Compat/Breaking
Component/Enclave-Builder
Component/Infrastructure
Deploy/BYOC
Deploy/Full-managed
Deploy/Self-hosted
Interface/API
Interface/CLI
Interface/Git
Interface/Web
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
public/platform!457
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/reject-unsupported-egress"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Scope and documentation cleanup
Current head:
63f98c1676ea9a3135e934c0439f35c84b1fbbf7, one signed commit ondfb626b820e13c7c6fd45c116bd66e1676361ba6, preserving the existing author/date.The cleanup relative to
5a2e11d7953001cff964692d2db8782edc40e3b6removes onlydocs/network-policy.mdand the feature-added README section: 172 lines removed. README now matches main. Every runtime and test blob is unchanged. The PR-only file inventory is 18 paths; no agent files, campaign scripts or unrelated fixes were added.Exact-head local verification
Run on the current head in a sanitized environment with Rust 1.96.1 and
CARGO_BUILD_JOBS=16:make test-network-policy— passed: 11 lifecycle tests, 11 API/rendering/local-Caddy checks, and 15 real namespace packet tests using the production firewall template.make test-cli-install test-bootstrap— passed installer checks and all 10 bootstrap tests.unshare --user --map-root-user --net cargo test --manifest-path src/tap-framer/Cargo.toml tests::real_tap_is_up_and_lives_until_last_owned_fd_closes -- --ignored --exact— passed the real-TAP lifetime test.make test— exit 2, not a green full-suite result: 1,075 passed, 2 failed, 15 ignored before Cargo stopped. The two failures arehandlers::common::tests::public_key_lookup_failure_is_internalandhandlers::credentials::passkey::tests::same_account_duplicate_body_is_distinct_from_cross_account. Both were previously reproduced on exact maindfb626b8; gateway sources and workspace dependency files remain identical to that baseline.git diff --check dfb626b8...HEADand clean integration with main — passed.Focused counts overlap the regular suite and must not be added to it. The docs companion also has a passing production build, six network examples validated through the real HCL/config parser, and a rendered local-link check. Earlier Clippy findings were baseline-reproduced; Clippy was not rerun for this docs-only delta.
Remaining rollout qualification
No cloud deployment or production validation was performed for this cleanup. Local packet/proxy/bootstrap checks do not establish actual AWS cloud-init, security-group attachment, native vsock/Nitro integration or live S3/IAM behavior. A focused exact-runtime AWS/Nitro networking smoke test remains required before rollout; a full BYOC business-flow suite is not a blanket merge prerequisite.
The PR remains draft; no merge or deployment is implied by this update.
Reject unsupported egress restrictionsto WIP: enforce enclave ingress and egress allowlists30ead510fcto0ddc14424d7e657f3c5atoc0e5319dead986011de9tof4e812a0b6f4e812a0b6to3ef81d75df3ef81d75dfto5a2e11d7955a2e11d795to63f98c167663f98c1676to8a3e193d63WIP: enforce enclave ingress and egress allowliststo enforce enclave ingress and egress allowlists