Bug 874518 - SELinux is preventing /usr/lib/systemd/systemd-timedated from 'read' accesses on the chr_file rtc0.
Summary: SELinux is preventing /usr/lib/systemd/systemd-timedated from 'read' accesses...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:443c231eacfe5e7b9b9c0dbaa3d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-08 11:07 UTC by Jiri Eischmann
Modified: 2012-11-08 12:09 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-08 12:09:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: type (9 bytes, text/plain)
2012-11-08 11:07 UTC, Jiri Eischmann
no flags Details
File: hashmarkername (14 bytes, text/plain)
2012-11-08 11:07 UTC, Jiri Eischmann
no flags Details

Description Jiri Eischmann 2012-11-08 11:07:13 UTC
Description of problem:
1. turned network time off in GNOME system settings
2. adjusted time manually
3. turned network time back on


Additional info:
libreport version: 2.0.17
kernel:         3.6.5-2.fc18.i686

description:
:SELinux is preventing /usr/lib/systemd/systemd-timedated from 'read' accesses on the chr_file rtc0.
:
:*****  Plugin catchall (100. confidence) suggests  ***************************
:
:If you believe that systemd-timedated should be allowed read access on the rtc0 chr_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:
:# grep systemd-timedat /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:
:Additional Information:
:Source Context                system_u:system_r:gnomeclock_t:s0
:Target Context                system_u:object_r:clock_device_t:s0
:Target Objects                rtc0 [ chr_file ]
:Source                        systemd-timedat
:Source Path                   /usr/lib/systemd/systemd-timedated
:Port                          <Neznámé>
:Host                          (removed)
:Source RPM Packages           systemd-195-2.fc18.i686
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.11.1-43.fc18.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.6.5-2.fc18.i686 #1 SMP Thu Nov 1
:                              01:02:26 UTC 2012 i686 i686
:Alert Count                   3
:First Seen                    2012-11-08 13:01:00 CET
:Last Seen                     2012-11-08 12:01:00 CET
:Local ID                      37e5e991-0c17-4448-bd28-f41702980d8f
:
:Raw Audit Messages
:type=AVC msg=audit(1352372460.4:340): avc:  denied  { read } for  pid=2063 comm="systemd-timedat" name="rtc0" dev="devtmpfs" ino=1166 scontext=system_u:system_r:gnomeclock_t:s0 tcontext=system_u:object_r:clock_device_t:s0 tclass=chr_file
:
:
:type=SYSCALL msg=audit(1352372460.4:340): arch=i386 syscall=open success=no exit=EACCES a0=b7750c92 a1=88000 a2=0 a3=b89c80a8 items=0 ppid=1 pid=2063 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemd-timedat exe=/usr/lib/systemd/systemd-timedated subj=system_u:system_r:gnomeclock_t:s0 key=(null)
:
:Hash: systemd-timedat,gnomeclock_t,clock_device_t,chr_file,read
:
:audit2allow
:
:#============= gnomeclock_t ==============
:allow gnomeclock_t clock_device_t:chr_file read;
:
:audit2allow -R
:
:#============= gnomeclock_t ==============
:allow gnomeclock_t clock_device_t:chr_file read;
:

Comment 1 Jiri Eischmann 2012-11-08 11:07:17 UTC
Created attachment 640734 [details]
File: type

Comment 2 Jiri Eischmann 2012-11-08 11:07:19 UTC
Created attachment 640735 [details]
File: hashmarkername

Comment 3 Miroslav Grepl 2012-11-08 12:09:26 UTC
Please update your policy. It has been fixed in the latest policy.


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