Repository navigation
security: enforce authority and pin browser egress - #8
Merged
Merged
Conversation
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
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.
Scope
Integrates fail-closed API authority and browser navigation policy, then removes the browser-side
DNS time-of-check/time-of-use gap with a per-session pinned egress proxy.
Exact candidate head:
3efaa528a18fb7dd60a85a4b395bd7d5e7f31936Security properties
(host, port) -> numeric addressesconnection plans.oversized buffers, and timeout paths fail closed.
through a complete same-host HTTPS proxy tuple with an exact loopback peer.
interpretation plus the unsafe import-string application entrypoint are disabled.
first and cannot be replaced by a no-op test callback.
Validation state
Local Python execution is intentionally disabled while the workstation is under a guarded memory
floor. The bounded hosted validator is the execution gate for hash-locked install, formatting,
lint, strict type checking, and tests. Independent adversarial exact-head review is also required.
Ready evidence
33521141440passed the exact candidate head.finding.
Container/noVNC acceptance remains a separate integration lane and is not claimed here.