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 1494172 - RHEL-7.5 should NOT contain any permissive domains
Summary: RHEL-7.5 should NOT contain any permissive domains
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.5
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
Mirek Jahoda
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-21 15:05 UTC by Lukas Vrabec
Modified: 2018-04-10 12:44 UTC (History)
8 users (show)

Fixed In Version: selinux-policy-3.13.1-174.el7
Doc Type: Enhancement
Doc Text:
_selinux-policy_ no longer contains permissive domains As a security hardening measure, the *SELinux* policy now does not set the following domains to permissive mode by default: * blkmapd_t * hsqldb_t * ipmievd_t * sanlk_resetd_t * systemd_hwdb_t * targetd_t The default mode for these domains is now set to enforcing.
Clone Of:
Environment:
Last Closed: 2018-04-10 12:43:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 3398551 0 None None None 2018-04-09 11:16:58 UTC
Red Hat Product Errata RHBA-2018:0763 0 None None None 2018-04-10 12:44:27 UTC

Description Lukas Vrabec 2017-09-21 15:05:03 UTC
$ cat permissivedomains.cil 
(roleattributeset cil_gen_require system_r)
(optional permissivedomains_optional_2
    (typeattributeset cil_gen_require blkmapd_t)
    (typepermissive blkmapd_t)
)
(optional permissivedomains_optional_3
    (typeattributeset cil_gen_require hsqldb_t)
    (typepermissive hsqldb_t)
)
(optional permissivedomains_optional_4
    (typeattributeset cil_gen_require ipmievd_t)
    (typepermissive ipmievd_t)
)
(optional permissivedomains_optional_5
    (typeattributeset cil_gen_require targetd_t)
    (typepermissive targetd_t)
)
(optional permissivedomains_optional_6
    (typeattributeset cil_gen_require systemd_hwdb_t)
    (typepermissive systemd_hwdb_t)
)
(optional permissivedomains_optional_7
    (typeattributeset cil_gen_require sanlk_resetd_t)
    (typepermissive sanlk_resetd_t)
)

Permissivedomain.cil file should be empty.

Comment 7 errata-xmlrpc 2018-04-10 12:43:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0763


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