Bug 235942

Summary: Updatedb is getting SELinux avc denied message
Product: [Fedora] Fedora Reporter: G.Wolfe Woodbury <redwolfe>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mitr
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Current Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-08-22 14:16:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
SETroubleshooter report none

Description G.Wolfe Woodbury 2007-04-10 22:24:27 UTC
Description of problem:
    SETroubleshooter shows an avc message for updatedb as detailed in the
attached report.


Version-Release number of selected component (if applicable):
    mlocate-0.16
    selinux-policy-targeted-2.5.11-5


How reproducible:
    unknown


Steps to Reproduce:
1.
2.
3.
  
Actual results:
    avc report as attached

Expected results:
    no avc report

Additional info:
work1.private: rawhide of 2007-04-09 default install (no updates or extras yet)
  Celeron(Coppermine) @600MHz   MSI mobo VIA chipset  160MB Maxtor PATA drive
  Trident video + ATI video (dual head)   RTL NIC  etc.

Comment 1 G.Wolfe Woodbury 2007-04-10 22:24:27 UTC
Created attachment 152184 [details]
SETroubleshooter report

Comment 2 Miloslav Trma─Ź 2007-04-10 22:35:29 UTC
Related to #234827 - updatedb needs to perform realpath() on all mount points. 
Thus, at least lstat () should be allowed for _all possible_ mount point
contexts; if there is another mount point in the subtree, updatedb should have
the permission necessary to lookup the mount point path within the subtree.

Comment 3 Daniel Walsh 2007-05-17 15:46:07 UTC
Fixed in selinux-policy-2.6.4-4.fc7

Comment 4 Daniel Walsh 2007-08-22 14:16:19 UTC
Should be fixed in the current release