Bug 1254565 - SELinux is preventing Google Chrome from using the setcap access on a process
SELinux is preventing Google Chrome from using the setcap access on a process
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy (Show other bugs)
All Linux
high Severity unspecified
: rc
: ---
Assigned To: Lukas Vrabec
Milos Malik
: ZStream
Depends On: 1251996
  Show dependency treegraph
Reported: 2015-08-18 08:03 EDT by Jan Kurik
Modified: 2015-09-02 10:16 EDT (History)
9 users (show)

See Also:
Fixed In Version: selinux-policy-3.13.1-23.el7_1.14
Doc Type: Bug Fix
Doc Text:
Due to SELinux preventing /opt/google/chrome-beta/chrome from using the setcap access on a process, the Google Chrome process previously terminated unexpectedly and the sandbox initialization failed. This update adds the chrome_sandbox_t SELinux policy, and Google Chrome no longer crashes in the described scenario.
Story Points: ---
Clone Of: 1251996
Last Closed: 2015-09-02 04:46:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Kurik 2015-08-18 08:03:49 EDT
This bug has been copied from bug #1251996 and has been proposed
to be backported to 7.1 z-stream (EUS).
Comment 4 Lukas Vrabec 2015-08-18 08:18:50 EDT
commit 29679ccc9b2bce7a16cb895c4eae3d8c0bc54931
Author: Lukas Vrabec <lvrabec@redhat.com>
Date:   Tue Aug 18 09:57:50 2015 +0200

    Allow chrome setcap to itself.
    Resolves: #1254565
Comment 8 errata-xmlrpc 2015-09-02 04:46:04 EDT
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.


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