Summary:

SELinux is preventing gvfs-fuse-daemo "read write" access on fuse.

Detailed Description:

[SELinux is in permissive mode. This access was not denied.]

SELinux denied access requested by gvfs-fuse-daemo. It is not expected that this
access is required by gvfs-fuse-daemo and this access may signal an intrusion
attempt. It is also possible that the specific version or configuration of the
application is causing it to require additional access.

Allowing Access:

You can generate a local policy module to allow this access - see FAQ
(http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Please file a bug
report.

Additional Information:

Source Context                sysadm_u:sysadm_r:oddjob_mkhomedir_t:s0-s0:c0.c102
                              3
Target Context                system_u:object_r:fuse_device_t:s0
Target Objects                fuse [ chr_file ]
Source                        gvfs-fuse-daemo
Source Path                   gvfs-fuse-daemo
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.7.19-69.fc13
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Plugin Name                   catchall
Host Name                     (removed)
Platform                      Linux (removed) 2.6.34.7-61.fc13.i686
                              #1 SMP Tue Oct 19 04:42:47 UTC 2010 i686 i686
Alert Count                   3
First Seen                    Thu 20 Jan 2011 10:51:25 PM MST
Last Seen                     Thu 20 Jan 2011 10:51:25 PM MST
Local ID                      90dcd2ef-bf7d-421b-b33f-9878bc1bfaa2
Line Numbers                  

Raw Audit Messages            

node=(removed) type=AVC msg=audit(1295589085.477:25925): avc:  denied  { read write } for  pid=1857 comm="gvfs-fuse-daemo" name="fuse" dev=devtmpfs ino=9089 scontext=sysadm_u:sysadm_r:oddjob_mkhomedir_t:s0-s0:c0.c1023 tcontext=system_u:object_r:fuse_device_t:s0 tclass=chr_file

node=(removed) type=AVC msg=audit(1295589085.477:25925): avc:  denied  { open } for  pid=1857 comm="gvfs-fuse-daemo" name="fuse" dev=devtmpfs ino=9089 scontext=sysadm_u:sysadm_r:oddjob_mkhomedir_t:s0-s0:c0.c1023 tcontext=system_u:object_r:fuse_device_t:s0 tclass=chr_file

node=(removed) type=AVC msg=audit(1295589085.477:25925): avc:  denied  { module_request } for  pid=1857 comm="gvfs-fuse-daemo" kmod="char-major-10-229" scontext=sysadm_u:sysadm_r:oddjob_mkhomedir_t:s0-s0:c0.c1023 tcontext=system_u:system_r:kernel_t:s0 tclass=system



Hash String generated from  catchall,gvfs-fuse-daemo,oddjob_mkhomedir_t,fuse_device_t,chr_file,read,write
audit2allow suggests:

#============= oddjob_mkhomedir_t ==============
#!!!! The source type 'oddjob_mkhomedir_t' can write to a 'chr_file' of the following types:
# null_device_t, zero_device_t, devtty_t

allow oddjob_mkhomedir_t fuse_device_t:chr_file { read write open };
#!!!! This avc can be allowed using the boolean 'domain_kernel_load_modules'

allow oddjob_mkhomedir_t kernel_t:system module_request;