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

info messages to firewall #1

Merged
merged 6 commits into from
Sep 26, 2022
Merged

info messages to firewall #1

merged 6 commits into from
Sep 26, 2022

Conversation

nyxnor
Copy link
Contributor

@nyxnor nyxnor commented Sep 26, 2022

https://forums.whonix.org/t/print-ports-opened-in-the-firewall/15469/4

the gateway message is more complete
for the workstation, I didn't know what to put, so only EXTERNAL and INTERNAL ports were mentioned.

I didn't find where it is opening INTERNAL_OPEN_PORTS, so this message is not printed.

also make the script be called by path, so easier to test by placing script at /usr/local/bin
usr/bin/whonix_firewall Outdated Show resolved Hide resolved
@nyxnor
Copy link
Contributor Author

nyxnor commented Sep 26, 2022

all changes done

@@ -365,6 +373,7 @@ ipv4_output() {
## https://phabricator.whonix.org/T533#11025
if [ "$firewall_mode" = "timesync-fail-closed" ]; then
local socks_port_item
[ "${info_enabled}" = "1" ] && output_cmd "INFO: not opening Internal TCP ports ${INTERNAL_OPEN_PORTS}, except 9108 for sdwdate, because firewall_mode=$firewall_mode"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually I think this is useful. So useful that I'll drop "${info_enabled}" = "1" after merge. That is because firewall mode timesync-fail-closed will be a challenge usability wise anyhow. Therefore this messages seems helpful and not too verbose.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great, thanks

@adrelanos adrelanos merged commit 67760a6 into Whonix:master Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants