Debian Bug report logs - #604081
Does not show password mismatch when first entered root password is empty

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Daniel Pocock <[email protected]>

To: [email protected]

Subject: root password mismatch

Date: Sat, 20 Nov 2010 01:24:31 +0100

Package: installation-reports

Installing amd64 as a domU in xen

At the first prompt for root password, just hit enter

At the second prompt, type a password

No password-mismatch error is displayed, installer proceeds to setting 
up a user account

Once rebooted, root login impossible using blank password or the 
`repeat' password

Mount the root fs (e.g. from dom0 or another OS), inspect /etc/shadow:

root:!:14932:0:99999:7:::


/etc/shadow can be fixed by copying an entry from a working /etc/shadow file

Message #10 received at [email protected] (full text, mbox, reply):

From: Christian PERRIER <[email protected]>

To: Daniel Pocock <[email protected]>, [email protected]

Subject: Re: Bug#604081: root password mismatch

Date: Sat, 20 Nov 2010 08:11:54 +0100

[Message part 1 (text/plain, inline)]

reassign 604081 user-setup
retitle 604081 Does not show password mismatch when first entered root password is empty
thanks

Quoting Daniel Pocock ([email protected]):
> Package: installation-reports
> 
> Installing amd64 as a domU in xen
> 
> At the first prompt for root password, just hit enter
> 
> At the second prompt, type a password
> 
> No password-mismatch error is displayed, installer proceeds to
> setting up a user account
> 
> Once rebooted, root login impossible using blank password or the
> `repeat' password
> 
> Mount the root fs (e.g. from dom0 or another OS), inspect /etc/shadow:
> 
> root:!:14932:0:99999:7:::

When the root password is empty, root account is disabled. This is
what the first template says.

Still, one can understand that entering the pwd empty, then setting
something in the confirmation is user error and the user should have a
chance to correct it. And we should anyway to give the false
impression that a root password will be set.

Reassigning to user-setup as this bug belongs to that package.


Thanks for pointing it.

[signature.asc (application/pgp-signature, inline)]

Message #19 received at [email protected] (full text, mbox, reply):

From: Cyril Brulebois <[email protected]>

To: Christian PERRIER <[email protected]>, [email protected]

Cc: Daniel Pocock <[email protected]>

Subject: Re: Bug#604081: root password mismatch

Date: Sun, 2 Mar 2014 15:46:24 +0100

[Message part 1 (text/plain, inline)]

Control: found -1 1.48
Control: found -1 1.55
Control: tag -1 confirmed

Christian PERRIER <[email protected]> (2010-11-20):
> reassign 604081 user-setup
> retitle 604081 Does not show password mismatch when first entered root password is empty
> thanks
> 
> Quoting Daniel Pocock ([email protected]):
> > Package: installation-reports
> > 
> > Installing amd64 as a domU in xen
> > 
> > At the first prompt for root password, just hit enter
> > 
> > At the second prompt, type a password
> > 
> > No password-mismatch error is displayed, installer proceeds to
> > setting up a user account
> > 
> > Once rebooted, root login impossible using blank password or the
> > `repeat' password
> > 
> > Mount the root fs (e.g. from dom0 or another OS), inspect /etc/shadow:
> > 
> > root:!:14932:0:99999:7:::
> 
> When the root password is empty, root account is disabled. This is
> what the first template says.
> 
> Still, one can understand that entering the pwd empty, then setting
> something in the confirmation is user error and the user should have a
> chance to correct it. And we should anyway to give the false
> impression that a root password will be set.
> 
> Reassigning to user-setup as this bug belongs to that package.

Still the case in wheezy and above, so recording the versions
accordingly.

Mraw,
KiBi.

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.