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 1213409 - selinux-policy: Update for abrt changes
Summary: selinux-policy: Update for abrt changes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Jan Zarsky
URL:
Whiteboard:
Depends On: 1212885 1213408
Blocks: 1211224 1214172 1295396
TreeView+ depends on / blocked
 
Reported: 2015-04-20 13:47 UTC by Florian Weimer
Modified: 2016-11-04 02:18 UTC (History)
8 users (show)

Fixed In Version: selinux-policy-3.13.1-66.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 02:18:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2283 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2016-11-03 13:36:25 UTC

Description Florian Weimer 2015-04-20 13:47:21 UTC 
The root directory for the problem directories will likely move back to /var/spool/abrt, where it was in RHEL 6 (bug 1213408).

If we have a separate crashdump handler which does not write user coredumps, we can restrict write access to problem directories only (bug 1212885).
Comment 2 Miroslav Grepl 2015-08-04 14:52:02 UTC 
What is a problem here? Is it still actual?
Comment 3 Florian Weimer 2015-08-04 15:46:12 UTC 
See bug 1212885.  A policy update is required once this is implemented.

Right now, abrt-hook-ccpp is not constrained by SELinux at all, and this seems rather difficult to change because it has to write all across the file system.
Comment 5 Florian Weimer 2015-08-24 11:18:21 UTC 
(In reply to Miroslav Grepl from comment #4)
> It is RHEL-7.2 material?
> 
> Basically we want to play witb abrt_exec_t labeling for this hook.

I don't think further constraints are possible until the user coredump functionality is split into a separate binary.  As far as I understan the situation, this must happen before it is possible to write a decent policy for abrt-hook-ccpp because right now, this program must be able to create arbitrary files, with arbitrary ownership, in arbitrary directories.
Comment 7 Miroslav Grepl 2016-01-14 09:06:42 UTC 
We have in Fedora policy

/usr/libexec/abrt-hook-ccpp     --  gen_context(system_u:object_r:abrt_dump_oops_exec_t,s0)

We need to back port it.
Comment 8 Mike McCune 2016-03-28 22:59:28 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 12 errata-xmlrpc 2016-11-04 02:18:34 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://rhn.redhat.com/errata/RHBA-2016-2283.html
Note You need to log in before you can comment on or make changes to this bug.