Skip to content
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

Merged
merged 3 commits into from
Dec 20, 2021
Merged

Improve interface settings #2011

merged 3 commits into from
Dec 20, 2021

Conversation

DL6ER
Copy link
Member

@DL6ER DL6ER commented Dec 19, 2021

By submitting this pull request, I confirm the following:

  • I have read and understood the contributors guide, as well as this entire template.
  • I have made only one major change in my proposed changes.
  • I have commented my proposed changes within the code.
  • I have tested my proposed changes, and have included unit tests where possible.
  • I am willing to help maintain this change if there are issues with it later.
  • I give this submission freely and claim no ownership.
  • It is compatible with the EUPL 1.2 license
  • I have squashed any insignificant commits. (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

…simply "Interface settings") to address issue #2009

Signed-off-by: DL6ER <[email protected]>
@DL6ER
Copy link
Member Author

DL6ER commented Dec 19, 2021

Screenshot of the updated settings:

Screenshot from 2021-12-19 10-02-39

@yubiuser
Copy link
Member

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?

@DL6ER
Copy link
Member Author

DL6ER commented Dec 19, 2021

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.

style/pi-hole.css Outdated Show resolved Hide resolved
@DL6ER
Copy link
Member Author

DL6ER commented Dec 20, 2021

Updated screenshot
interface-settings

@yubiuser yubiuser merged commit d7e750b into devel Dec 20, 2021
@yubiuser yubiuser deleted the tweak/interface_settings branch December 20, 2021 20:38
@DL6ER DL6ER mentioned this pull request Dec 22, 2021
@pralor-bot
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants