Repository navigation
fix: harden localhost server boundary - #175
Merged
Merged
Conversation
Start #173 by failing closed on non-loopback binds and adding browser security headers at the Node server boundary.
Member
Author
|
/mira pause |
Contributor
Mira PR Walkthrough❌ Review failed — click for detailsThe code review failed to complete due to an unexpected error. Stage: Code review |
Added security headers and tests for loopback host validation.
4 tasks done
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.
/mira pause
A bounded first localhost UI hardening slice for #173.
What changed
Why
The setup/status UI must not become reachable on the LAN or embeddable/executable by an untrusted website.
Checks
npm testnpm run check