Summary:

SELinux is preventing /usr/lib64/chromium-browser/chrome-sandbox access to a
leaked /dev/tty1 file descriptor.

Detailed Description:

[chrome-sandbox has a permissive type (chrome_sandbox_t). This access was not
denied.]

SELinux denied access requested by the chrome-sandbox command. It looks like
this is either a leaked descriptor or chrome-sandbox output was redirected to a
file it is not allowed to access. Leaks usually can be ignored since SELinux is
just closing the leak and reporting the error. The application does not use the
descriptor, so it will run properly. If this is a redirection, you will not get
output in the /dev/tty1. You should generate a bugzilla on selinux-policy, and
it will get routed to the appropriate package. You can safely ignore this avc.

Allowing Access:

You can generate a local policy module to allow this access - see FAQ
(http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385)

Additional Information:

Source Context                unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c
                              0.c1023
Target Context                unconfined_u:object_r:user_tty_device_t:s0
Target Objects                /dev/tty1 [ chr_file ]
Source                        chrome-sandbox
Source Path                   /usr/lib64/chromium-browser/chrome-sandbox
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           chromium-4.0.227.0-0.1.20091027svn30269.fc12
Target RPM Packages           
Policy RPM                    selinux-policy-3.6.32-41.fc12
Selinux Enabled               True
Policy Type                   targeted
MLS Enabled                   True
Enforcing Mode                Enforcing
Plugin Name                   leaks
Host Name                     (removed)
Platform                      Linux (removed) 2.6.31.5-127.fc12.x86_64 #1 SMP
                              Sat Nov 7 21:11:14 EST 2009 x86_64 x86_64
Alert Count                   1
First Seen                    Sun 15 Nov 2009 09:53:38 PM CST
Last Seen                     Sun 15 Nov 2009 09:53:38 PM CST
Local ID                      9d42bcb4-f034-46ed-ae6f-b05573d228c6
Line Numbers                  

Raw Audit Messages            

node=(removed) type=AVC msg=audit(1258293218.419:36328): avc:  denied  { read write } for  pid=8321 comm="chrome-sandbox" path="/dev/tty1" dev=tmpfs ino=2315 scontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_tty_device_t:s0 tclass=chr_file

node=(removed) type=SYSCALL msg=audit(1258293218.419:36328): arch=c000003e syscall=59 success=yes exit=0 a0=2d4e7a8 a1=2d4e5f0 a2=2d4eaa0 a3=7fff3eb90c60 items=0 ppid=8257 pid=8321 auid=500 uid=500 gid=500 euid=0 suid=0 fsuid=0 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm="chrome-sandbox" exe="/usr/lib64/chromium-browser/chrome-sandbox" subj=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 key=(null)



Hash String generated from  selinux-policy-3.6.32-41.fc12,leaks,chrome-sandbox,chrome_sandbox_t,user_tty_device_t,chr_file,read,write
audit2allow suggests:

#============= chrome_sandbox_t ==============
allow chrome_sandbox_t user_tty_device_t:chr_file { read write };