fix(bridge): add Host/Origin guard + bearer token to HTTP bridge#20
Merged
Conversation
macieju-opera
force-pushed
the
fix/bridge-auth-hardening
branch
2 times, most recently
from
a1ec20b to
9065687
Compare
- Reject non-loopback Host on every route (kills DNS rebinding) - Reject non-loopback Origin (kills browser CSRF; CLI sends none) - Require a per-instance bearer token on /call, /tools, /last-snapshot; /health stays token-free for port detection - Generate the token in runBridge, persist it 0600 in the PID file, and read it back in the client to attach Authorization on protected calls
macieju-opera
force-pushed
the
fix/bridge-auth-hardening
branch
from
9065687 to
a864cac
Compare
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
2 participants
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.
/health stays token-free for port detection
read it back in the client to attach Authorization on protected calls