Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 119193

Summary: slocate can not find anything.
Product: [Fedora] Fedora Reporter: Aleksey Nogin <aleksey>
Component: policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: pgraner, russell
Target Milestone: ---Keywords: SELinux
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.10.1-5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-07 18:41:54 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:
Bug Depends On:    
Bug Blocks: 122683    

Description Aleksey Nogin 2004-03-26 06:23:11 UTC
When I run locate from staff_r, I get a bunch of messages of the form

audit(1080282148.605:0): avc:  denied  { read } for  pid=7704
exe=/usr/bin/slocate name=xxxx dev=hda2 ino=1573113
scontext=aleksey:staff_r:staff_locate_t
tcontext=aleksey:object_r:staff_home_t tclass=lnk_file
audit(1080282148.620:0): avc:  denied  { read } for  pid=7704
exe=/usr/bin/slocate name=yyyy dev=hda2 ino=1409767
scontext=aleksey:staff_r:staff_locate_t
tcontext=aleksey:object_r:staff_home_t tclass=lnk_file

(where names all match the pattern I was trying to locate) and slocate
does not print any matches.

I am currently using policy-sources-1.9-15

Comment 1 Daniel Walsh 2004-03-26 14:42:17 UTC
What are you trying to slocate?

Dan

Comment 2 Aleksey Nogin 2004-03-26 19:37:09 UTC
No matter what I try to locate, if I run "locate xyz" under staff_r,
it never works (and I have to run it under sudo to get any output)...

Comment 3 Daniel Walsh 2004-04-08 13:36:54 UTC
Added allow rule to policy-1.10-1-5


Comment 4 Aleksey Nogin 2004-05-07 18:41:54 UTC
This has been working correctly for a while now.