Warn about what I am about to break/automated review of rules
Bug #1103480 reported by
costales
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gufw |
Fix Released
|
Undecided
|
costales |
Bug Description
For example, if I block outgoing port 80 I would like a Pro and Con list of reasons why it is a good and a bad idea to block this port. Like an automated security review.
“This rule will prevent the following programs from behaving as expected:\n* Web browsers\n* Most web integration.\n\n This is only recommended in a very limited environment.”
Or even smart-service usage detection:
“The open gajim process appears to be a XMPP client* but you have not opened the relevant service ports. Would you like to create rules for that?”
* Based on open ports/sockets mapped against registered TCP port usage.
description: | updated |
summary: |
- Warn about what I am about to break + Warn about what I am about to break/automated review of rules |
To post a comment you must log in.
The use-case is obviously to offer novice users an automated review of what problems their firewall may create for them. With the assertion that users are indeed very likely to configure their system in a way that will interrupt their normal use of their system.
Expert users may spot errors or omissions in their configuration.