Bug 911357 - SELinux is preventing chrome from read, write access on the file /SYSV00000000 (deleted).
Summary: SELinux is preventing chrome from read, write access on the file /SYSV0000000...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 17
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c37a5d33d8b91cea014c4147096...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-14 20:10 UTC by fabioballack_13
Modified: 2013-07-04 10:07 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-04 10:07:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: type (9 bytes, text/plain)
2013-02-14 20:10 UTC, fabioballack_13
no flags Details
File: hashmarkername (14 bytes, text/plain)
2013-02-14 20:10 UTC, fabioballack_13
no flags Details

Description fabioballack_13 2013-02-14 20:10:08 UTC
Additional info:
libreport version: 2.0.18
kernel:         3.7.3-101.fc17.i686

description:
:SELinux is preventing chrome from read, write access on the file /SYSV00000000 (deleted).
:
:*****  Plugin restorecon (99.5 confidence) suggests  *************************
:
:If você deseja reparar este rótulo.
:/SYSV00000000 (deleted) rótulo padrão deve ser etc_runtime_t.
:Then você pode executar o restorecon.
:Do
:# /sbin/restorecon -v /SYSV00000000 (deleted)
:
:*****  Plugin catchall (1.49 confidence) suggests  ***************************
:
:If você acredita que o chrome deva ser permitido acesso de read write em SYSV00000000 (deleted) file  por default.
:Then você precisa reportar este como um erro.
:Você pode gerar um módulo de política local para permitir este acesso.
:Do
:permitir este acesso agora executando:
:# grep chrome /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:
:Additional Information:
:Source Context                unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c
:                              0.c1023
:Target Context                system_u:object_r:tmpfs_t:s0
:Target Objects                /SYSV00000000 (deleted) [ file ]
:Source                        chrome
:Source Path                   chrome
:Port                          <Desconhecido>
:Host                          (removed)
:Source RPM Packages           
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-167.fc17.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.7.3-101.fc17.i686 #1 SMP Fri Jan
:                              18 17:52:48 UTC 2013 i686 i686
:Alert Count                   1
:First Seen                    2013-02-14 15:55:14 BRT
:Last Seen                     2013-02-14 15:55:14 BRT
:Local ID                      fcc2d6b3-3205-41c4-b891-96c612e4746b
:
:Raw Audit Messages
:type=AVC msg=audit(1360868114.143:94): avc:  denied  { read write } for  pid=7462 comm="chrome" path=2F535953563030303030303030202864656C6574656429 dev="tmpfs" ino=1048577 scontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file
:
:
:Hash: chrome,chrome_sandbox_t,tmpfs_t,file,read,write
:
:audit2allow
:
:#============= chrome_sandbox_t ==============
:allow chrome_sandbox_t tmpfs_t:file { read write };
:
:audit2allow -R
:
:#============= chrome_sandbox_t ==============
:allow chrome_sandbox_t tmpfs_t:file { read write };
:

Comment 1 fabioballack_13 2013-02-14 20:10:11 UTC
Created attachment 697372 [details]
File: type

Comment 2 fabioballack_13 2013-02-14 20:10:14 UTC
Created attachment 697373 [details]
File: hashmarkername

Comment 3 Miroslav Grepl 2013-02-15 13:56:38 UTC
Are you able to reproduce it? Have you ever run in permissive mode?

Comment 4 Daniel Walsh 2013-02-15 14:14:19 UTC
I think I saw this happen when users run wine apps.

We have a fix for that in F18/F19 policy.

Comment 5 fabioballack_13 2013-02-16 05:26:08 UTC
No, i haven't wine.
I've no idea why it happens... Its very stranger for me.

Comment 6 Daniel Walsh 2013-02-18 16:27:37 UTC
How about this command.

 sesearch -T -s unconfined_dbusd_t  | grep tmpfs
   type_transition unconfined_dbusd_t tmpfs_t : file user_tmpfs_t;

Comment 7 Fedora End Of Life 2013-07-04 00:56:31 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.


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