Bug 688521 - Cannot login into root with "su -"
Summary: Cannot login into root with "su -"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: coreutils
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-17 09:54 UTC by Joachim Backes
Modified: 2011-03-17 13:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-17 13:54:01 UTC
Type: ---


Attachments (Terms of Use)
/etc/nsswitch.conf (1.68 KB, text/plain)
2011-03-17 12:56 UTC, Joachim Backes
no flags Details
Output of ausearch -m AVC (1.33 MB, text/plain)
2011-03-17 12:57 UTC, Joachim Backes
no flags Details

Description Joachim Backes 2011-03-17 09:54:29 UTC
Description of problem:
I'm logged in as user backes, then I try: "su -". I enter the correct pwd, but the login is rejected because of incorrect password.

Logging in in some console is possible, and "sudo su -" too.

Version-Release number of selected component (if applicable):
coreutils-8.10-2.fc15.x86_64

How reproducible:
always

Steps to Reproduce:
1.su -
2.Enter root pwd
3.
  
Actual results:
su: incorrect password

Expected results:
Login performed


Additional info:
/var/log/secure in that case:

Mar 17 10:46:26 eule unix_chkpwd[15372]: check pass; user unknown
Mar 17 10:46:33 eule unix_chkpwd[15374]: check pass; user unknown
Mar 17 10:46:33 eule unix_chkpwd[15374]: password check failed for user (root)
Mar 17 10:46:33 eule su: pam_unix(su-l:auth): authentication failure; logname=backes uid=500 euid=500 tty=pts/0 ruser=backes rhost=  user=root

Comment 1 Ondrej Vasik 2011-03-17 11:52:26 UTC
Adding PAM maintainer to CC as he may have some insight to it/what to check. PAM support was consolidated with SUSE (it means rewritten) in 8.7-1.fc15 - and noone complained so far, so I wonder what went wrong on your machine. Is the issue new (caused by some update) or you have just installed the brand new F-15 and updated packages?

Comment 2 Tomas Mraz 2011-03-17 12:19:21 UTC
Are there any SELinux AVCs? 'ausearch -m AVC'

What is in your /etc/nsswitch.conf?

Comment 3 Joachim Backes 2011-03-17 12:55:18 UTC
(In reply to comment #2)
> Are there any SELinux AVCs? 'ausearch -m AVC'
> 
> What is in your /etc/nsswitch.conf?

1. Selinux is disabled
2. /etc/nsswitch.conf: See attachment
3. ausearch -m AVC: see attachment

Comment 4 Joachim Backes 2011-03-17 12:56:10 UTC
Created attachment 485997 [details]
/etc/nsswitch.conf

Comment 5 Joachim Backes 2011-03-17 12:57:21 UTC
Created attachment 485999 [details]
Output of ausearch -m AVC

Comment 6 Joachim Backes 2011-03-17 13:02:27 UTC
(In reply to comment #1)
> Adding PAM maintainer to CC as he may have some insight to it/what to check.
> PAM support was consolidated with SUSE (it means rewritten) in 8.7-1.fc15 - and
> noone complained so far, so I wonder what went wrong on your machine. Is the
> issue new (caused by some update) or you have just installed the brand new F-15
> and updated packages?

This is a fresh installed F15. I have a similar problem: after locking screen, I cannot unlock screen (passwd is not accepted: BZ 684653)

Comment 7 Joachim Backes 2011-03-17 13:10:51 UTC
(In reply to comment #6)
> (In reply to comment #1)
> > Adding PAM maintainer to CC as he may have some insight to it/what to check.
> > PAM support was consolidated with SUSE (it means rewritten) in 8.7-1.fc15 - and
> > noone complained so far, so I wonder what went wrong on your machine. Is the
> > issue new (caused by some update) or you have just installed the brand new F-15
> > and updated packages?
> 
> This is a fresh installed F15. I have a similar problem: after locking screen,
> I cannot unlock screen (passwd is not accepted: BZ 684653)

Sorry: I meant: this is a fresh installed F15 *+ all actual updates*

Comment 8 Tomas Mraz 2011-03-17 13:15:47 UTC
What 'ls -l /bin/su' prints?

Ondrej, were there any setuid related changes in su recently? The 'uid=500 euid=500' in the log message above actually looks very suspicious.

Comment 9 Tomas Mraz 2011-03-17 13:16:53 UTC
And also  output of 'ls -l /sbin/unix_chkpwd' please.

Comment 10 Joachim Backes 2011-03-17 13:30:45 UTC
(In reply to comment #9)
> And also  output of 'ls -l /sbin/unix_chkpwd' please.

-rwsr-xr-x. 1 root root 32000 Feb  8 15:19 /sbin/unix_chkpwd

Comment 11 Ondrej Vasik 2011-03-17 13:32:02 UTC
No, I'm not aware of any such change, su should still be suid root:root (4755) ...

Comment 12 Joachim Backes 2011-03-17 13:40:03 UTC
By setting the s-bit in /bin/su, getting rid from my su problems :-(

I don't know why it was lost.

Thanks for your support :-)

JB

Comment 13 Ondrej Vasik 2011-03-17 13:54:01 UTC
I checked the koji build and suid is present there, so closing NOTABUG. Feel free (to reopen and reassign) if you find out what cleared the suid...


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