Bug 1919479

Summary: /usr/bin/which fails to locate executable where access is granted by group membership
Product: Red Hat Enterprise Linux 7 Reporter: Richard Brittain <richard.brittain>
Component: whichAssignee: Than Ngo <than>
Status: CLOSED INSUFFICIENT_DATA QA Contact: CS System Management SST QE <rhel-cs-system-management-subsystem-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.9CC: lagordon
Target Milestone: rcFlags: than: needinfo? (richard.brittain)
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-17 18:35:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Richard Brittain 2021-01-22 23:55:37 UTC 
Description of problem:
Programs in $PATH which are executable by virtue of group permissions, but are not 'other RX', are not found by /usr/bin/which, but can be executed by the shells.

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

How reproducible:
100%

Steps to Reproduce:
1. Remove other RX from any executable in any directory in $PATH
2. Change the group, if needed, to one that you are a member of
3. /usr/bin/which will report it cannot find the changed executable
4. bash and tcsh will both find and execute the program.

Actual results:
/usr/bin/which: no XXX in ( /directory:.... )

Expected results:
full path to first matching executable in $PATH

Additional info:
Discovered while setting up application software for which the license requires that we use a restricted group for access.
Built-in which command for tcsh works as expected.
Comment 2 Than Ngo 2021-03-05 12:51:28 UTC 
I cannot reproduce the problem with your steps. 
Could you please add testcase how i can reproduce the problem?

Thanks
Comment 3 Than Ngo 2021-03-17 18:35:48 UTC 
I'm closing that bugzilla INSUFFICIENT_DATA because there's no testcase to reproduce this issue.  Feel free to reopen it once you find some way how to reproduce it.
Thanks