Thank you for you report. Please note that for usability a default
ruleset is put in use by design and documented in the ufw(8) man page.
Users are free to fine-tune those defaults for site-specific needs as
described in the ufw-framework(8) man page. As a result option 'a' is
out of scope. Option 'b' does make sense and is something that can be
looked at with 'status verbose' (implementation-wise it might make sense
to check if all the defaults are in use and if they are, mention those
defaults, and if they are not, mention that custom rules are in effect.
I'm not sure yet how this should be represented in the UI.
** Summary changed:
- ufw still allows incoming packets when policy is set to deny
+ ufw allows certain incoming packets when policy is set to deny
** Information type changed from Private Security to Public
** Summary changed:
- ufw allows certain incoming packets when policy is set to deny
+ 'ufw status verbose' should mention some details of the default ruleset
** Changed in: ufw (Ubuntu)
Status: New => Triaged
** Changed in: ufw (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820350
Title:
'ufw status verbose' should mention some details of the default
ruleset
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1820350/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
