-
-
Notifications
You must be signed in to change notification settings - Fork 562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve interface settings #2011
Conversation
…simply "Interface settings") to address issue #2009 Signed-off-by: DL6ER <[email protected]>
…ally bind to an interface. Signed-off-by: DL6ER <[email protected]>
Before we had the warning text only in regard to "all origins". Now we include "respond" (previously "listen") and "bind" into this section. Did our judgement about the danger and firewall necessity change? |
Yes, imagine a user configures a Pi-hole running on a cloud server to listen on the outside interface. Without a firewall this immediately becomes an open resolver. |
Signed-off-by: DL6ER <[email protected]>
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/pi-hole-ftl-v5-12-web-v5-9-and-core-v5-7-released/51795/1 |
By submitting this pull request, I confirm the following:
git rebase
)What does this PR aim to accomplish?:
Fix #2009
How does this PR accomplish the above?:
Add new option to really bind to the specified interface and take care that the description does not imply we are doing this with the other options. See the referenced issue ticket for why this is confusing.
Accompanying pull requests:
What documentation changes (if any) are needed to support this PR?:
See pi-hole/docs#620