Bug 691068

Summary: SELinux is preventing /usr/bin/gdb from 'write' accesses on the directory /usr/share/glib-2.0/gdb.
Product: [Fedora] Fedora Reporter: John Watzke <watzkej>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: dwalsh, jan.kratochvil, mgrepl, pmuldoon, sergiodj, tromey
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:f37cca7ad06aafa7b91e3cf98287a5db96b34e38c10baecab77434db4f311a3f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-28 11:22:40 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 John Watzke 2011-03-26 14:17:10 UTC
SELinux is preventing /usr/bin/gdb from 'write' accesses on the directory /usr/share/glib-2.0/gdb.

*****  Plugin catchall_labels (83.8 confidence) suggests  ********************

If you want to allow gdb to have write access on the gdb directory
Then you need to change the label on /usr/share/glib-2.0/gdb
Do
# semanage fcontext -a -t FILE_TYPE '/usr/share/glib-2.0/gdb'
where FILE_TYPE is one of the following: gconf_home_t, pcscd_var_run_t, xkb_var_lib_t, xdm_rw_etc_t, xdm_home_t, pam_var_console_t, cgroup_t, var_lock_t, root_t, tmp_t, var_t, user_home_dir_t, locale_t, var_auth_t, user_fonts_t, user_tmpfs_t, tmpfs_t, xdm_spool_t, fonts_cache_t, user_tmp_t, auth_cache_t, xdm_tmpfs_t, var_spool_t, var_lib_t, var_run_t, xserver_log_t, xdm_tmp_t, var_log_t, xdm_log_t, gnome_home_type, pam_var_run_t, xdm_var_lib_t, xdm_var_run_t. 
Then execute: 
restorecon -v '/usr/share/glib-2.0/gdb'


*****  Plugin catchall (17.1 confidence) suggests  ***************************

If you believe that gdb should be allowed write access on the gdb 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 gdb /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:usr_t:s0
Target Objects                /usr/share/glib-2.0/gdb [ dir ]
Source                        gdb
Source Path                   /usr/bin/gdb
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           gdb-7.2.50.20110305-28.fc15
Target RPM Packages           glib2-devel-2.28.2-1.fc15
Policy RPM                    selinux-policy-3.9.16-1.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed)
                              2.6.38-0.rc8.git0.1.fc15.i686.PAE #1 SMP Tue Mar 8
                              08:16:43 UTC 2011 i686 i686
Alert Count                   16
First Seen                    Tue 08 Mar 2011 10:16:22 PM CST
Last Seen                     Tue 08 Mar 2011 10:19:20 PM CST
Local ID                      5e486ebf-baf3-4871-82e6-5b3af83fa5fa

Raw Audit Messages
type=AVC msg=audit(1299644360.934:127): avc:  denied  { write } for  pid=2046 comm="gdb" name="gdb" dev=dm-1 ino=3024986 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:usr_t:s0 tclass=dir


type=SYSCALL msg=audit(1299644360.934:127): arch=i386 syscall=open success=no exit=EACCES a0=bfc0d8ab a1=82c1 a2=81a4 a3=9cbf968 items=0 ppid=2045 pid=2046 auid=4294967295 uid=0 gid=500 euid=0 suid=0 fsuid=0 egid=500 sgid=500 fsgid=500 tty=(none) ses=4294967295 comm=gdb exe=/usr/bin/gdb subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null)

Hash: gdb,xdm_t,usr_t,dir,write

audit2allow

#============= xdm_t ==============
#!!!! The source type 'xdm_t' can write to a 'dir' of the following types:
# var_spool_t, xserver_log_t, var_lib_t, var_run_t, xdm_tmp_t, faillog_t, var_log_t, xdm_log_t, gnome_home_type, pam_var_run_t, xdm_var_lib_t, xdm_var_run_t, gconf_home_t, pcscd_var_run_t, xkb_var_lib_t, xdm_rw_etc_t, xdm_home_t, pam_var_console_t, cgroup_t, var_lock_t, root_t, tmp_t, user_home_dir_t, var_t, locale_t, var_auth_t, user_fonts_t, user_tmpfs_t, tmpfs_t, xdm_spool_t, fonts_cache_t, user_tmp_t, auth_cache_t, xdm_tmpfs_t

allow xdm_t usr_t:dir write;

audit2allow -R

#============= xdm_t ==============
#!!!! The source type 'xdm_t' can write to a 'dir' of the following types:
# var_spool_t, xserver_log_t, var_lib_t, var_run_t, xdm_tmp_t, faillog_t, var_log_t, xdm_log_t, gnome_home_type, pam_var_run_t, xdm_var_lib_t, xdm_var_run_t, gconf_home_t, pcscd_var_run_t, xkb_var_lib_t, xdm_rw_etc_t, xdm_home_t, pam_var_console_t, cgroup_t, var_lock_t, root_t, tmp_t, user_home_dir_t, var_t, locale_t, var_auth_t, user_fonts_t, user_tmpfs_t, tmpfs_t, xdm_spool_t, fonts_cache_t, user_tmp_t, auth_cache_t, xdm_tmpfs_t

allow xdm_t usr_t:dir write;

Comment 1 Jan Kratochvil 2011-03-28 11:22:40 UTC

*** This bug has been marked as a duplicate of bug 528554 ***