Bug 786389 - SELinux is preventing /usr/libexec/colord from 'read' accesses on the None 023.
Summary: SELinux is preventing /usr/libexec/colord from 'read' accesses on the None 023.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:44fa8a0bee8a39fb93077fbe446...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-01 10:22 UTC by Patryk Zawadzki
Modified: 2013-02-13 18:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 18:50:43 UTC
Type: ---


Attachments (Terms of Use)

Description Patryk Zawadzki 2012-02-01 10:22:01 UTC
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.2.2-1.fc16.x86_64
reason:         SELinux is preventing /usr/libexec/colord from 'read' accesses on the None 023.
time:           śro, 1 lut 2012, 11:21:21

description:
:SELinux is preventing /usr/libexec/colord from 'read' accesses on the None 023.
:
:*****  Plugin catchall (100. confidence) suggests  ***************************
:
:If aby colord powinno mieć domyślnie read dostęp do 023 <Nieznane>.
:Then proszę to zgłosić jako błąd.
:Można utworzyć lokalny moduł polityki, aby umożliwić ten dostęp.
:Do
:można tymczasowo zezwolić na ten dostęp wykonując polecenia:
:# grep colord /var/log/audit/audit.log | audit2allow -M mojapolityka
:# semodule -i mojapolityka.pp
:
:Additional Information:
:Source Context                system_u:system_r:colord_t:s0-s0:c0.c1023
:Target Context                system_u:object_r:device_t:s0
:Target Objects                023 [ None ]
:Source                        colord
:Source Path                   /usr/libexec/colord
:Port                          <Nieznane>
:Host                          (removed)
:Source RPM Packages           colord-0.1.15-2.fc16.x86_64
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-74.fc16.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.2.2-1.fc16.x86_64
:                              #1 SMP Thu Jan 26 03:21:58 UTC 2012 x86_64 x86_64
:Alert Count                   1
:First Seen                    śro, 1 lut 2012, 11:15:57
:Last Seen                     śro, 1 lut 2012, 11:15:57
:Local ID                      84fad1d4-7400-486c-9b5a-576f024b0a64
:
:Raw Audit Messages
:type=AVC msg=audit(1328091357.26:67): avc:  denied  { read } for  pid=1928 comm="colord" name="023" dev=devtmpfs ino=23333 scontext=system_u:system_r:colord_t:s0-s0:c0.c1023 tcontext=system_u:object_r:device_t:s0 tclass=chr_filenode=(removed) type=SYSCALL msg=audit(1328091357.026:67): arch=c000003e syscall=2 success=no exit=-13 a0=7fff511ca010 a1=0 a2=7fff511ca024 a3=28 items=0 ppid=1 pid=1928 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="colord" exe="/usr/libexec/colord" subj=system_u:system_r:colord_t:s0-s0:c0.c1023 key=(null)
:
:
:Hash: colord,colord_t,device_t,None,read
:
:audit2allow
:
:
:audit2allow -R
:
:

Comment 1 Daniel Walsh 2012-02-01 20:08:19 UTC
It looks like you have a mislabeled chr_file 023?

Do you have 23 usb devices on your machine?

Comment 2 Patryk Zawadzki 2012-02-02 10:26:03 UTC
No, just a mouse so with all the internals I guess I have around 10 devices recognized total.

Comment 3 Daniel Walsh 2012-02-02 20:31:49 UTC
Strange it would generate device 023.  I have updated policy to generate the first 30 with the correct label, but this is probably a race condition and can be safely ignored.  Has it happened again?

Comment 4 Patryk Zawadzki 2012-02-02 20:40:50 UTC
No, I've only seen it happen this one time.

Comment 5 Daniel Walsh 2012-02-02 20:55:32 UTC
Ok don't worry about it. 

When the kernel creates the device, it is labeled based on the directory device_t. when udev sees it, it relabels it to usb_device_t.  If colord gets at it before udev, then you get this AVC, which really does not matter.

find /dev -name 023

Should show you which device it was.

Comment 6 Fedora End Of Life 2013-01-16 15:42:48 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Fedora End Of Life 2013-02-13 18:50:47 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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