Bug 912147

Summary: SELinux is preventing /usr/libexec/gvfs-udisks2-volume-monitor from 'read' accesses on the directory /mnt/30445625-b757-4213-96d8-986d7a37767b.
Product: [Fedora] Fedora Reporter: Carlos Manso <chiecc>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dominick.grift, dwalsh, mgrepl
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:6fe93a8dcd44e87cd9a734bc013f48946a9f438fc6d7c73aeaf308d812342de3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-14 03:00:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Carlos Manso 2013-02-17 21:15:21 UTC
Description of problem:
SELinux is preventing /usr/libexec/gvfs-udisks2-volume-monitor from 'read' accesses on the directory /mnt/30445625-b757-4213-96d8-986d7a37767b.

*****  Plugin restorecon (82.4 confidence) suggests  *************************

If you want to fix the label. 
/mnt/30445625-b757-4213-96d8-986d7a37767b default label should be mnt_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /mnt/30445625-b757-4213-96d8-986d7a37767b

*****  Plugin file (7.05 confidence) suggests  *******************************

If you think this is caused by a badly mislabeled machine.
Then you need to fully relabel.
Do
touch /.autorelabel; reboot

*****  Plugin file (7.05 confidence) suggests  *******************************

If you think this is caused by a badly mislabeled machine.
Then you need to fully relabel.
Do
touch /.autorelabel; reboot

*****  Plugin catchall_labels (4.59 confidence) suggests  ********************

If you want to allow gvfs-udisks2-volume-monitor to have read access on the 30445625-b757-4213-96d8-986d7a37767b directory
Then you need to change the label on /mnt/30445625-b757-4213-96d8-986d7a37767b
Do
# semanage fcontext -a -t FILE_TYPE '/mnt/30445625-b757-4213-96d8-986d7a37767b'
where FILE_TYPE is one of the following: device_t, hwdata_t, locale_t, etc_t, fonts_t, sysfs_t, tmpfs_t, cgroup_t, xdm_t, var_log_t, var_lock_t, bin_t, cert_t, init_t, lib_t, mnt_t, var_lib_t, var_run_t, root_t, tmp_t, usr_t, configfile, etc_t, domain, pam_var_run_t, user_tmp_t, cert_t, xdm_tmpfs_t, device_t, user_fonts_t, locale_t, etc_t, admin_home_t, xdm_dbusd_t, xdm_spool_t, fonts_cache_t, abrt_t, sssd_public_t, base_ro_file_type, lib_t, man_t, selinux_config_t, root_t, usr_t, xserver_log_t, dbusd_etc_t, user_home_t, alsa_etc_rw_t, user_home_dir_t, systemd_unit_file_type, sysctl_dev_t, sysctl_net_t, default_context_t, rpm_var_cache_t, cache_home_t, data_home_t, gconf_etc_t, autofs_t, device_t, device_t, var_auth_t, proc_net_t, var_spool_t, proc_t, cgroup_t, var_log_t, config_usr_t, xdm_log_t, bin_t, init_var_run_t, gnome_home_type, pcscd_var_run_t, textrel_shlib_t, var_lib_t, var_run_t, udev_var_run_t, xkb_var_lib_t, var_t, xdm_tmp_t, user_home_type, xdm_rw_etc_t, rpm_var_lib_t, user_tmp_t, samba_etc_t, xdm_var_lib_t, xdm_var_run_t, auth_home_t, auth_cache_t, inotifyfs_t, gnome_home_t, selinux_login_config_t, ecryptfs_t, var_lib_t, systemd_logind_var_run_t, systemd_passwd_var_run_t, gconf_home_t, sysctl_kernel_t, samba_etc_t, admin_home_t, net_conf_t, user_tmpfs_type, systemd_logind_sessions_t, var_run_t, ssh_home_t, accountsd_var_lib_t, proc_t, user_home_dir_t, xdm_home_t, pam_var_console_t, sysctl_crypto_t, security_t, faillog_t, sysctl_kernel_t, tmp_t, security_t, nscd_var_run_t, krb5_host_rcache_t. 
Then execute: 
restorecon -v '/mnt/30445625-b757-4213-96d8-986d7a37767b'


*****  Plugin catchall (1.31 confidence) suggests  ***************************

If you believe that gvfs-udisks2-volume-monitor should be allowed read access on the 30445625-b757-4213-96d8-986d7a37767b directory 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 gvfs-udisks2-vo /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:file_t:s0
Target Objects                /mnt/30445625-b757-4213-96d8-986d7a37767b [ dir ]
Source                        gvfs-udisks2-vo
Source Path                   /usr/libexec/gvfs-udisks2-volume-monitor
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           gvfs-1.14.2-2.fc18.i686
Target RPM Packages           
Policy RPM                    selinux-policy-3.11.1-76.fc18.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.7.7-201.fc18.i686 #1 SMP Tue Feb
                              12 22:59:10 UTC 2013 i686 i686
Alert Count                   4
First Seen                    2013-02-17 22:08:32 CET
Last Seen                     2013-02-17 22:08:32 CET
Local ID                      113e6db6-c214-4317-93c7-eacd06c65fe6

Raw Audit Messages
type=AVC msg=audit(1361135312.853:358): avc:  denied  { read } for  pid=1340 comm="gvfs-udisks2-vo" name="/" dev="sda4" ino=2 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:file_t:s0 tclass=dir


type=SYSCALL msg=audit(1361135312.853:358): arch=i386 syscall=openat success=no exit=EACCES a0=ffffff9c a1=94f90d8 a2=98800 a3=0 items=0 ppid=1339 pid=1340 auid=42 uid=42 gid=42 euid=42 suid=42 fsuid=42 egid=42 sgid=42 fsgid=42 ses=1 tty=(none) comm=gvfs-udisks2-vo exe=/usr/libexec/gvfs-udisks2-volume-monitor subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null)

Hash: gvfs-udisks2-vo,xdm_t,file_t,dir,read

audit2allow

#============= xdm_t ==============
allow xdm_t file_t:dir read;

audit2allow -R

#============= xdm_t ==============
allow xdm_t file_t:dir read;


Additional info:
hashmarkername: setroubleshoot
kernel:         3.7.7-201.fc18.i686
type:           libreport

Comment 1 Miroslav Grepl 2013-02-18 11:34:56 UTC
You will need to fix labeling using

# restorecon -R -v /mnt/30445625-b757-4213-96d8-986d7a37767b

Comment 2 Daniel Walsh 2013-02-18 15:29:16 UTC
Why would the login program want to look at that file?

Comment 3 Carlos Manso 2013-03-07 00:00:16 UTC
I don't know, but it should be a bug since this happens in a fresh F18 installation.

Comment 4 Daniel Walsh 2013-03-07 16:19:20 UTC
1f5e9fa27d0feb0b051bef1d4fe0356fb43735f7 fixes this in Rawhide.  Basically I dontaudit xdm_t listing any directories.

Comment 5 Carlos Manso 2013-03-07 16:57:49 UTC
Btw, I didn't say it, sorry, but this happens when I use the gnome-disk program to mount the partition at boot.

Comment 6 Miroslav Grepl 2013-03-11 15:00:56 UTC
Backported.

Comment 7 Fedora Update System 2013-03-12 13:55:28 UTC
selinux-policy-3.11.1-85.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2013-3605/selinux-policy-3.11.1-85.fc18

Comment 8 Fedora Update System 2013-03-12 23:35:24 UTC
Package selinux-policy-3.11.1-85.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-85.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3605/selinux-policy-3.11.1-85.fc18
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2013-03-14 03:00:34 UTC
selinux-policy-3.11.1-85.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.