https://bugs.kde.org/show_bug.cgi?id=434952
Bug ID: 434952
Summary: Support firewalld services / UFW application profiles
Product: systemsettings
Version: unspecified
Platform: unspecified
URL: https://invent.kde.org/plasma/plasma-firewall/-/issues
/14
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_firewall
Assignee: plasma-b...@kde.org
Reporter: kevin.kof...@chello.at
CC: tcanabr...@kde.org
Target Milestone: ---
Looking at the code here and the screenshot under
https://www.omgubuntu.co.uk/2021/01/kde-plasma-5-21-features , it looks like,
just like its predecessor nx-firewall (formerly nomad-firewall),
plasma-firewall has no UI to pick one of the predefined application profiles
(firewalld calls them "services") known to firewalld or UFW, and open the ports
for it. Instead, you have to know the port number(s) to create a rule. This
makes the KCM impractical to use.
Please support the predefined application profiles of the underlying firewall
backend, which make it very easy to open up the ports for a given application.
See also: https://github.com/nx-desktop/nx-firewall/issues/15
--
You are receiving this mail because:
You are watching all bug changes.
