Bug 682950

Summary: update of gobject-introspection causes AVC
Product: [Fedora] Fedora Reporter: Tom London <selinux>
Component: gobject-introspectionAssignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dwalsh, mgrepl, otaylor, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 13:40:33 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 Tom London 2011-03-08 05:23:54 UTC
Description of problem:
After updating to gobject-introspection-0.10.3-1.fc15.x86_64 via 'yum update', I get the following AVC.

Possible leaked file descriptor?


SELinux is preventing /usr/sbin/prelink from read access on the file
/etc/gconf/schemas/metacity.schemas.

*****  Plugin catchall (100. confidence) suggests  ***************************

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

Additional Information:
Source Context                staff_u:system_r:prelink_t:s0-s0:c0.c1023
Target Context                system_u:object_r:gconf_etc_t:s0
Target Objects                /etc/gconf/schemas/metacity.schemas [ file ]
Source                        prelink
Source Path                   /usr/sbin/prelink
Port                          <Unknown>
Host                          tlondon.localhost.org
Source RPM Packages           prelink-0.4.4-1.fc15
Target RPM Packages           metacity-2.30.3-5.fc15
Policy RPM                    selinux-policy-3.9.15-5.fc16
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     tlondon.localhost.org
Platform                      Linux tlondon.localhost.org
                             2.6.38-0.rc6.git6.1.fc15.x86_64 #1 SMP Sat Feb 26
                             01:14:56 UTC 2011 x86_64 x86_64
Alert Count                   4
First Seen                    Fri 25 Feb 2011 07:08:44 AM PST
Last Seen                     Thu 03 Mar 2011 06:27:08 AM PST
Local ID                      4124f12e-524b-425c-8830-bd86b4573154

Raw Audit Messages
type=AVC msg=audit(1299162428.844:75): avc:  denied  { read } for
pid=3459 comm="prelink" path="/etc/gconf/schemas/metacity.schemas"
dev=dm-0 ino=3789 scontext=staff_u:system_r:prelink_t:s0-s0:c0.c1023
tcontext=system_u:object_r:gconf_etc_t:s0 tclass=file


type=SYSCALL msg=audit(1299162428.844:75): arch=x86_64 syscall=execve
success=yes exit=0 a0=40e194 a1=7fff2c223ff0 a2=7fff2c2299b8
a3=7f5a374cb9f0 items=0 ppid=3457 pid=3459 auid=500 uid=0 gid=0 euid=0
suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=1 comm=prelink
exe=/usr/sbin/prelink subj=staff_u:system_r:prelink_t:s0-s0:c0.c1023
key=(null)

Hash: prelink,prelink_t,gconf_etc_t,file,read

audit2allow

#============= prelink_t ==============
allow prelink_t gconf_etc_t:file read;

audit2allow -R

#============= prelink_t ==============
allow prelink_t gconf_etc_t:file read;


Version-Release number of selected component (if applicable):
gobject-introspection-0.10.3-1.fc15.x86_64

How reproducible:


Steps to Reproduce:
1. 'yum update'
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Daniel Walsh 2011-03-08 13:44:55 UTC
Colin, we are thinking this might be a leaked file descriptor.  Does gobject open

/etc/gconf/schemas/metacity.schemas

?

Comment 2 Fedora End Of Life 2013-04-03 17:59:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 3 Tom London 2014-06-09 13:26:59 UTC
Very old bug.

No longer see this.

Comment 4 Fedora End Of Life 2015-01-09 16:36:03 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 5 Fedora End Of Life 2015-02-17 13:40:33 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.