Bug#317012: Bug#328090: [Pkg-shadow-devel] Bug#317012: fixed in shadow 1:4.0.3-37

[Nicolas François]

Hello,

I've not been able to reproduce this bug with adduser 3.67 or 3.67.0 and the
shadow utilities 4.0.3-39.

I could not use ltsp-build-client to test, but I used another existing chroot.
I just did:
shadowconfig off,
checked the passwd and adduser versions,
and then installed ssh 3.8.1p1-8.sarge.4 without any problem (adduser
issue the "chage failed with return code 3, shadow not enabled, password
aging cannot be set. Continuing." message, and continue).

On Fri, Sep 23, 2005 at 01:00:21PM +0200, mhdebian-packages at zugschlus.de wrote:
> On Fri, Sep 23, 2005 at 10:08:36AM +0200, Christian Perrier wrote:
> > Hmmm, we chould maybe check the versions of adduser and passwd in the chroot..
> 
> That information is already available in the bug report. adduser
> 3.67.0 and passwd 4.0.3-39.

Peter mentionned recently that he used:
ltsp-build-client --dist etch --mirror http://ftp.skolelinux.no/debian

4.0.3-39 is not in etch (the last testing version is 4.0.3-35, which do
not have the special return code).

I tried with adduser 3.67.0 and passwd 4.0.3-35, and I had the same issue
described in the original bug.
("chage: can't open shadow password file...Aborting.")

So Peter, just to be sure, is 4.0.3-39 the version installed in the
chroot, or the version on the chroot host?
(Since I don't know how you fixed the dependencies to successfully
debootstrap, maybe you took sid's passwd).


> > Once we solve this, I think your problem won't be solved
> > completely. adduser will still fail, I think.
> 
> Recent addusers will ignore the error and continue with a warning.
> This is _generally_ the case, but some adduser/passwd combinations
> will still fail since chage changed the "no shadow" exit code recently.

This seems to work nicely (and sorry about the "no shadow" exit code change).

Kind Regards,
-- 
Nekral