feat(windows): add host-mediated driver loopback bridge - #146
Merged
Merged
Conversation
added 11 commits
September 27, 2026 01:49
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.
Adds Windows parity for loopback-only Driver Host authority without granting ambient network to the LPAC child. Driver Host reserves a LOCAL Named Pipe before spawn, passes only the Host-controlled pipe path, then authorizes the exact AppContainer SID and validates the exact child PID/session before proxying. Host owns the 127.0.0.1 listener and bridges bounded connections to the pipe. Godot consumes the same WebSocket protocol over NamedPipeClient. Adds a dedicated Windows x64/ARM64 round-trip gate proving TCP Host -> LPAC pipe -> child echo while manifest.network remains false. Unix loopback behavior is preserved.