Bug 68729

Summary: su doesn't set permissions at the right point
Product: [Retired] Red Hat Linux Reporter: Ben Woodard <woodard>
Component: sh-utilsAssignee: Tim Waugh <twaugh>
Status: CLOSED NEXTRELEASE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-04 20:20:11 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:
Attachments:
Description Flags
patch which fixes the problem none

Description Ben Woodard 2002-07-12 22:33:28 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606

Description of problem:
This is a continuation of the bug
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=66862

The problem with the solution that I presented in that bug is the fact that it
still doesn't handle the case where the only access to the file is through a
secondary group. Therefore, just doing a setfsgid doesn't work in all situations.

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


How reproducible:
Always

Steps to Reproduce:
1. adduser test1
2. add a group test2
3. add test1 user to test2 group.
4. chmod 750 /home
5. chgrp test2 /home
6. chmod 700 /home/test1
7. su - test1


Additional info:
Comment 1 Ben Woodard 2002-07-12 22:34:07 UTC 
Created attachment 65189 [details]
patch which fixes the problem
Comment 2 Bernhard Rosenkraenzer 2002-08-29 18:45:21 UTC 
Fixed in 2.0.12-3
Comment 3 Bill Nottingham 2006-08-04 20:20:11 UTC 
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.

However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.