UFW does not support GUFW names from terminal

Bug #1783622 reported by Omadas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gufw
Triaged
Undecided
Unassigned

Bug Description

The only option to label additions to ufw is comment:

~ $ sudo ufw allow 80 comment 'example'

if a user opens up gufx they will see:

No Rule Name
1 80 ALLOW IN Anywhere # example

Notice this adds the common '#' to comment out the text we added after 'coment' in our command, but when oppened in GUFW, it does not read this comment as the name.

As part of this feature request I would like to have either:
1) A command-line option to add a name in UFW
-&/OR-
2) GUFW to store and read the Name Column in the same way UFW adds comments

Tags: gufw ufw
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This seems like a bug in gufw not parsing the ufw output correctly. gufw could also instead import ufw python files and implement something similar to src/frontend.py and work with the UFWRule class instead of parsing ufw output which might make it easier to maintain.

affects: ufw → gui-ufw
costales (costales)
Changed in gui-ufw:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.