fix(security): secure default host binding to loopback#576
Open
niStee wants to merge 1 commit into
Open
Conversation
Owner
|
谢 PR,思路对的 — 默认开 0.0.0.0 确实是个 expose 风险。但当前 patch 会让 Docker 部署破: [P1] 容器内 loopback 监听让 publish 不可达 — 建议方向:
|
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.
The default host binding of
::inadvertently exposes the proxy to the entire local network, which can be a security risk for a local development proxy. This patch locks the default binding to127.0.0.1to ensure safe local-only isolation. Users who explicitly want network access can override it in their config.