Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 171175

Summary: PAM patches to /bin/su calls pam_setcred after environment copy
Product: Red Hat Enterprise Linux 3 Reporter: Craig Lawson <craig.lawson>
Component: coreutilsAssignee: Pete Graner <pgraner>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0   
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: 2007-10-19 18:52:37 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: 150056    
Bug Blocks:    

Description Craig Lawson 2005-10-19 02:57:20 UTC 
Description of problem:
pam_setcred gives the service modules a chance to set environment variables with
pam_putenv. On successful operation, the appplication may then copy the
accumulated PAM environment variables to the process environment with putenv(3).
login performs the environment copy after pam_open_session and pam_setcred have
been called. In contrast, su does it after pam_open_session but *before*
pam_setcred, and this is incorrect.

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

How reproducible:
100%

Additional info:
The PAM functionality is added to the GNU su.c with coreutils-4.5.2-pam.patch.
My platform is actually on WS 3.0.
Comment 1 Craig Lawson 2005-10-19 02:57:58 UTC 
See related bug 150056
Comment 2 RHEL Program Management 2007-10-19 18:52:37 UTC 
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.