Bug 113692

Summary: passwordless accounts report expired passwd after update
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Andreas Kleen <ak>
Component: BasesystemAssignee: Dr. Werner Fink <werner>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: jsuchome
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Andreas Kleen 2005-08-28 19:23:32 UTC 
I updated an machine from one of the previews (3 or 4 I think) to beta3
(I know it's not directly supported, but the bug seems generic) 

Now SuSEconfig always hangs while trying to configure tetex. Some investigation
shows that it hangs in su nobody -c ... because su nobody now does this 
(when invoked by hand):

# su nobody
Your password has expired. Choose a new password.
Old Password: 

The nobody account looks ok to me. The pam modules and coreutils rpms are also
correct (right version for beta3 and no verify errors). /etc/pam.d is identical
to another b3 machine without that problem.

# grep nobody /etc/shadow /etc/passwd
/etc/shadow:nobody:*:12961:0:0::::
/etc/passwd:nobody:x:65534:65533:nobody:/var/lib/nobody:/bin/bash

It also happens with other system accounts like news.

I compared it with a beta3 installation that doesn't have this problem and they
show

etc/passwd:nobody:x:65534:65533:nobody:/var/lib/nobody:/bin/bash
etc/shadow:nobody:*:13019::::::
Comment 1 Andreas Kleen 2005-08-28 19:26:26 UTC 
When I remove the :0:0 and replace it with :: it works as expected.
Comment 2 Dr. Werner Fink 2005-08-29 09:57:56 UTC 
Was this an update from Beta2?  If so we mark this as duplicate
from bug 103873
Comment 3 Andreas Kleen 2005-08-29 10:05:28 UTC 
No from an Preview. 3 or 4 I don't quite remember.

I would rather make that bug a duplicate of this because I provide
the solution (replacing :0:0 with :: helps) while he does not. It seems to be
the same problem though.

The bug is basically that pam_unix.so handles :0:0 as if the password was
already expired, which seems wrong.
Comment 4 Jiří Suchomel 2005-08-29 10:12:48 UTC 
The bug is solved from beta2: you write in comment #0 that beta3 is fine...

*** This bug has been marked as a duplicate of 103873 ***
Comment 5 Andreas Kleen 2005-08-29 10:26:10 UTC 
No beta3 is *NOT* fine. You misread my comment.  I had this problem
exactly with beta3.
Comment 6 Jiří Suchomel 2005-08-29 10:30:27 UTC 
I commented this:

"I compared it with a beta3 installation that doesn't have this problem ..."

That means: You had a problem with an update to beta3, because it was already
broken in your preview - this cannot be fixed by an update. If you install fresh
beta3, it will be fine.

*** This bug has been marked as a duplicate of 103873 ***