Bug 745643

Summary: SELinux is preventing /sbin/plymouthd from 'open' accesses on the chr_file tty1.
Product: [Fedora] Fedora Reporter: jeff <jcmj>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: dominick.grift, dwalsh, fedora, mgrepl, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:3276e4b1e7a973401a1fea822675cfe3ca354f975bb029682dce8b0067109d66
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 18:30:52 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 jeff 2011-10-12 21:47:39 UTC
SELinux is preventing /sbin/plymouthd from 'open' accesses on the chr_file tty1.

*****  Plugin catchall_boolean (89.3 confidence) suggests  *******************

If you want to allow all daemons the ability to read/write terminals
Then you must tell SELinux about this by enabling the 'allow_daemons_use_tty' boolean.
Do
setsebool -P allow_daemons_use_tty 1

*****  Plugin catchall (11.6 confidence) suggests  ***************************

If you believe that plymouthd should be allowed open access on the tty1 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 plymouthd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:plymouthd_t:s0
Target Context                unconfined_u:object_r:user_tty_device_t:s0
Target Objects                tty1 [ chr_file ]
Source                        plymouthd
Source Path                   /sbin/plymouthd
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           plymouth-0.8.4-0.20110510.2.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-35.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 2.6.40.3-0.fc15.x86_64 #1 SMP Tue
                              Aug 16 04:10:59 UTC 2011 x86_64 x86_64
Alert Count                   3
First Seen                    Thu 14 Jul 2011 05:22:05 PM CDT
Last Seen                     Thu 18 Aug 2011 03:23:51 PM CDT
Local ID                      697f2ff4-000d-47dd-8d99-0d8856173032

Raw Audit Messages
type=AVC msg=audit(1313699031.929:133): avc:  denied  { open } for  pid=2026 comm="plymouthd" name="tty1" dev=devtmpfs ino=4038 scontext=system_u:system_r:plymouthd_t:s0 tcontext=unconfined_u:object_r:user_tty_device_t:s0 tclass=chr_file


type=SYSCALL msg=audit(1313699031.929:133): arch=x86_64 syscall=open success=yes exit=ENOEXEC a0=dbf700 a1=102 a2=18 a3=0 items=0 ppid=1 pid=2026 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=plymouthd exe=/sbin/plymouthd subj=system_u:system_r:plymouthd_t:s0 key=(null)

Hash: plymouthd,plymouthd_t,user_tty_device_t,chr_file,open

audit2allow

#============= plymouthd_t ==============
#!!!! This avc can be allowed using the boolean 'allow_daemons_use_tty'

allow plymouthd_t user_tty_device_t:chr_file open;

audit2allow -R

#============= plymouthd_t ==============
#!!!! This avc can be allowed using the boolean 'allow_daemons_use_tty'

allow plymouthd_t user_tty_device_t:chr_file open;

Comment 1 Daniel Walsh 2011-10-13 14:43:10 UTC
Ray is there a reason whith plymouthd would open a terminal used by a user?

Comment 2 Fedora End Of Life 2012-08-07 18:30:54 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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