Bug 434952

Summary: Support firewalld services / UFW application profiles
Product: [Applications] systemsettings Reporter: Kevin Kofler <kevin.kofler>
Component: kcm_firewallAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: nate, tcanabrava
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
URL: https://invent.kde.org/plasma/plasma-firewall/-/issues/14
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Kevin Kofler 2021-03-25 21:38:56 UTC 
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
Comment 1 Nate Graham 2021-03-31 01:50:44 UTC 

*** This bug has been marked as a duplicate of bug 434935 ***