Bug 1370003

Summary: SELinux is preventing google-chrome from 'create' accesses on the file 63.
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: dapospis, dominick.grift, dwalsh, lvrabec, mgrepl, plautrba, vasben
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1697c8e5fbef234e1a8e2a886662e29447e42e035cef2e2b5d0c0e4eb95da607;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-08 19:21:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mikhail 2016-08-25 03:20:56 UTC
Description of problem:
SELinux is preventing google-chrome from 'create' accesses on the file 63.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that google-chrome should be allowed create access on the 63 file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'google-chrome' --raw | audit2allow -M my-googlechrome
# semodule -X 300 -i my-googlechrome.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1
                              023
Target Context                unconfined_u:object_r:unconfined_t:s0
Target Objects                63 [ file ]
Source                        google-chrome
Source Path                   google-chrome
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-191.13.fc24.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.7.2-200.fc24.x86_64+debug #1 SMP
                              Mon Aug 22 18:14:28 UTC 2016 x86_64 x86_64
Alert Count                   1
First Seen                    2016-08-25 08:12:37 YEKT
Last Seen                     2016-08-25 08:12:37 YEKT
Local ID                      547cd02a-4178-407b-a49a-e1d04861d49e

Raw Audit Messages
type=AVC msg=audit(1472094757.796:241): avc:  denied  { create } for  pid=2367 comm="google-chrome" name="63" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:unconfined_t:s0 tclass=file permissive=0


Hash: google-chrome,unconfined_t,unconfined_t,file,create

Version-Release number of selected component:
selinux-policy-3.13.1-191.13.fc24.noarch

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.7.2-200.fc24.x86_64+debug
type:           libreport

Comment 1 Mikhail 2016-08-25 03:23:09 UTC
Description of problem:
Just launch Google Chrome

Version-Release number of selected component:
selinux-policy-3.13.1-191.13.fc24.noarch

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.7.2-200.fc24.x86_64
type:           libreport

Comment 2 Mikhail 2016-08-26 19:44:56 UTC
Description of problem:
Just launch Google Chrome

Version-Release number of selected component:
selinux-policy-3.13.1-191.14.fc24.noarch

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.7.2-200.fc24.x86_64
type:           libreport

Comment 3 Daniel Walsh 2016-08-26 19:46:58 UTC
I'm running google-chrome-beta on Rawhide and have not seen this.

 rpm -q google-chrome-beta
google-chrome-beta-53.0.2785.80-1.x86_64

Comment 4 Mikhail 2016-08-26 19:51:06 UTC
My version is newer

$ rpm -qa | grep  google-chrome
google-chrome-unstable-54.0.2837.0-1.x86_64

Comment 5 Daniel Walsh 2016-08-27 10:01:00 UTC
That one is not available via dnf

# cat /etc/yum.repos.d/google-chrome-unstable.repo 
[google-chrome-unstable]
name=google-chrome-unstable
baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
enabled=1
gpgcheck=1
gpgkey=https://dl.google.com/linux/linux_signing_key.pub

dnf -y update google-chrome-beta
Last metadata expiration check: 0:31:29 ago on Sat Aug 27 05:28:11 2016.
Dependencies resolved.
Nothing to do.
Complete!

[root@dhcp-10-19-62-196 cache]# rpm -q google-chrome-beta
google-chrome-beta-53.0.2785.80-1.x86_64

I wonder if google removed it?

Comment 6 Mikhail 2016-08-27 10:50:13 UTC
https://www.chromium.org/getting-involved/dev-channel


We use different channels, please try:
# dnf install  google-chrome-unstable

Comment 7 Dalibor Pospíšil 2016-09-04 19:31:48 UTC
Description of problem:
Happens after reboot, when chrome browser starts.

Version-Release number of selected component:
selinux-policy-3.13.1-191.14.fc24.noarch

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.7.2-201.fc24.x86_64
type:           libreport

Comment 8 Daniel Walsh 2016-09-08 19:21:39 UTC

*** This bug has been marked as a duplicate of bug 1345836 ***