Bug 243088 - Incorrect pam service name for command "su -"
Summary: Incorrect pam service name for command "su -"
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: coreutils
Version: 5.0
Hardware: i686
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Ondrej Vasik
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-07 09:19 UTC by Phyt
Modified: 2008-08-13 13:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-13 13:49:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Phyt 2007-06-07 09:19:51 UTC
Description of problem:
"su -" transmit bad service name to pam ( "su-l" instead of "su" ) and refused
authentication (/etc/pam.d/other is use).  
add a service name su-l in /etc/pam.d/ and "su -" prompt for a password    

Version-Release number of selected component (if applicable):
coreutils-5.97-12.1.el5

How reproducible:
login with à non-root account
exec "su -"
Pam refused auhtentication (it's refer to default service (other).

Comment 1 Tim Waugh 2007-06-07 09:45:26 UTC
coreutils does ship a file /etc/pam.d/su-l for this.  What does 'rpm -V
coreutils' say?

Comment 2 Phyt 2007-06-07 12:06:34 UTC
Hi, 

Coreutils provide /etc/pam.d/su-l 

rpm -V coreutils :
missing   c /etc/pam.d/runuser
missing   c /etc/pam.d/runuser-l
S.5....T c /etc/pam.d/su
S.5....T c /etc/pam.d/su-l

Sorry, i don't verify it ... but i don't remove this file after default install.
( i'm going to seach why this file is missing ).     
 



Comment 3 Ondrej Vasik 2008-01-24 16:07:51 UTC
Hi, I'm new coreutils maintainer - is there something new? As Tim said , RHEL-5
coreutils are shipping /etc/pam.d/su-l (/etc/pam.d/runuser-l for runuser -) for
that so I'd like to know if I could close that bugzilla or if you found
something meanwhile...

Comment 4 Ondrej Vasik 2008-08-13 13:49:31 UTC
Closing INSUFFICIENT_DATA after more than 6 month without response, feel free to reopen it if you find something relevant about the problem (how it happened that the runuser pam files were misssing).


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