RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 993737 - gui: zones should be more visibly described
Summary: gui: zones should be more visibly described
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 980210
TreeView+ depends on / blocked
 
Reported: 2013-08-06 11:57 UTC by Tomas Dolezal
Modified: 2013-10-23 14:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-23 14:33:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tomas Dolezal 2013-08-06 11:57:18 UTC 
Description of problem:
Zones  should be more precisely described in firewall-config:
* what is their purpose (somewhere on the right, not in a tooltip)
* make visual difference between immutable and mutable zones
* immtuable zones should not be editable (firewalld-0.3.4-1.fc19.noarch bug!) and not even have options visible (because user won't see any difference between trusted/blocked/drop)

Version-Release number of selected component (if applicable):
firewalld-0.3.4-1

How reproducible:
always

Steps to Reproduce:
1. use firewall-config GUI

Expected results:
please fix or provide information why do you think it shouldn't be fixed this way
thanks

Additional info:
CCed affiliated users
Comment 3 Tomas Dolezal 2013-08-06 12:45:02 UTC 
please note that it also requires zone description, not only things connected with immutable zones
Comment 4 Jiri Popelka 2013-08-16 14:11:50 UTC 
(In reply to Tomáš Doležal from comment #0)
> Zones  should be more precisely described in firewall-config:
> * what is their purpose (somewhere on the right, not in a tooltip)

Do you mean individual zones or generally ?

> * make visual difference between immutable and mutable zones
> * immtuable zones should not be editable (firewalld-0.3.4-1.fc19.noarch
> bug!) and not even have options visible (because user won't see any
> difference between trusted/blocked/drop)

Well, this has been an intended change in 0.3.4.
We decided that the concept of 'immutable' uselessly complicates things, for example the biggest problem was that if you want to permanently add an interface to a zone you need to modify that zone and that was impossible with immutable zones. I don't think there's any use in restricting users what zones they can or can't modify. Initially we wanted to restrict the immutableness only on some entries like services/ports/etc. (which does not make a sense to add to a trusted/block/drop) but not on interfaces (which we need to be able to add to a trusted/block/drop). But because we had not seen a way how to do that (allow to modify/add only some entries) in GUI we decided to drop it completely.
Comment 5 Tomas Dolezal 2013-08-16 14:32:00 UTC 
(In reply to Jiri Popelka from comment #4)
> > Zones  should be more precisely described in firewall-config:
> > * what is their purpose (somewhere on the right, not in a tooltip)
> Do you mean individual zones or generally ?

for individual zones, to highlight their differences. important for formerly immutable zones.
I see major difference between block/drop in the default policy (reject or drop). In the mentioned release I did not find anything about it, only at wiki (and maybe manpage, which is for cli)

Is it possible to show/allow change the default policy?
Comment 6 Thomas Woerner 2013-10-23 14:33:17 UTC 
We do not have immutable zones anymore, all zones are mutable.

All zones are customizable, therefore there is no easy way to have descriptions for the zones that match the zone even after the user modified the zone.

Closing as CANTFIX.
Note You need to log in before you can comment on or make changes to this bug.