Bug 235942 - Updatedb is getting SELinux avc denied message
Updatedb is getting SELinux avc denied message
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2007-04-10 18:24 EDT by G.Wolfe Woodbury
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version: Current
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-22 10:16:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
SETroubleshooter report (2.31 KB, text/plain)
2007-04-10 18:24 EDT, G.Wolfe Woodbury
no flags Details

  None (edit)
Description G.Wolfe Woodbury 2007-04-10 18:24:27 EDT
Description of problem:
    SETroubleshooter shows an avc message for updatedb as detailed in the
attached report.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
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 18:24:27 EDT
Created attachment 152184 [details]
SETroubleshooter report
Comment 2 Miloslav Trmač 2007-04-10 18:35:29 EDT
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 11:46:07 EDT
Fixed in selinux-policy-2.6.4-4.fc7
Comment 4 Daniel Walsh 2007-08-22 10:16:19 EDT
Should be fixed in the current release

Note You need to log in before you can comment on or make changes to this bug.