Login passwords incorrect on some newly installed 1.0.1 systems

  • Done
  • quality assurance status badge
Details
3 participants
  • Andreas Enge
  • Ludovic Courtès
  • pelzflorian (Florian Pelz)
Owner
unassigned
Submitted by
pelzflorian (Florian Pelz)
Severity
normal
P
P
pelzflorian (Florian Pelz) wrote on 20 May 2019 11:38
(address . bug-guix@gnu.org)
20190520093855.3ldl2mjhgi3fx6qz@pelzflorian.localdomain
Login fails with

Login incorrect

on a system newly installed from the 1.0.1 ISO image — on only some
reinstalls. Maybe it was my fault, but maybe not, it is kind of
spooky. Can others reproduce?

The first time the password was correctly set to x in /etc/passwd and
in /etc/shadow the line looked normal. Maybe I made a typo when
setting up the password?

I tried to reproduce with a less sensitive password “y” for root and I
believe an empty user password or maybe “y” too; now I got no user
entry in /etc/passwd and /etc/shadow but can log in as root.

This was the content of /etc/passwd:

root:x:0:0::/root:/gnu/store/qn1ax1fkj16x280m1rv7mcimfmn9l2pf-bash-4.4.23/bin/bash
nobody:x:65534:997::/nonexistent:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder01:x:999:30000:Guix Build User 1:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder02:x:998:30000:Guix Build User 2:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder03:x:997:30000:Guix Build User 3:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder04:x:996:30000:Guix Build User 4:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder05:x:995:30000:Guix Build User 5:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder06:x:994:30000:Guix Build User 6:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder07:x:993:30000:Guix Build User 7:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder08:x:992:30000:Guix Build User 8:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder09:x:991:30000:Guix Build User 9:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
guixbuilder10:x:990:30000:Guix Build User 10:/var/empty:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
messagebus:x:989:983:D-Bus system bus user:/var/run/dbus:/gnu/store/dl8k19fivmv181d81lpn1nadsf219ky8-shadow-4.6/sbin/nologin
polkitd:x:988:982:Polkit daemon user:/var/empty:/run/current-system/profile/sbin/nologin

The content of /etc/shadow was

root:$6$vWBy92HZjt$P.g83qzyyuZ0AebfKjsS/gZV.1SlaMkUqsmsO9cP1yXtpsCIE.9gDNDtMVwZWa..wmvVNqjqgjg7OFhKadshF.:18036::::::
nobody:!:18036::::::
guixbuilder01:!:18036::::::
guixbuilder02:!:18036::::::
guixbuilder03:!:18036::::::
guixbuilder04:!:18036::::::
guixbuilder05:!:18036::::::
guixbuilder06:!:18036::::::
guixbuilder07:!:18036::::::
guixbuilder08:!:18036::::::
guixbuilder09:!:18036::::::
guixbuilder10:!:18036::::::
messagebus:!:18036::::::
polkitd:!:18036::::::

Maybe I turned off my computer at the wrong time when booting into the
installed system? But the passwords get set up before the first boot,
don’t they? I reinstalled again since then. Now it works.

Regards,
Florian
L
L
Ludovic Courtès wrote on 20 May 2019 17:01
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(address . 35806@debbugs.gnu.org)
87o93xrwyz.fsf@gnu.org
Hi!

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

Toggle quote (4 lines)
> on a system newly installed from the 1.0.1 ISO image — on only some
> reinstalls. Maybe it was my fault, but maybe not, it is kind of
> spooky. Can others reproduce?

No. (I did many installs in VMs before the release… :-))

Note that you can check by doing an install in a VM using the attached
script.

Toggle quote (4 lines)
> The content of /etc/shadow was
>
> root:$6$vWBy92HZjt$P.g83qzyyuZ0AebfKjsS/gZV.1SlaMkUqsmsO9cP1yXtpsCIE.9gDNDtMVwZWa..wmvVNqjqgjg7OFhKadshF.:18036::::::

So a password was set, as expected. Maybe you tried the wrong password,
or with the wrong keyboard layout?

Thanks,
Ludo’.
#!/bin/sh
set -e
set -x
ISO="$(./pre-inst-env guix system disk-image --file-system-type=iso9660 gnu/system/install.scm)"
qemu-img create -f qcow2 /tmp/t.img 10G

#EFI_OPTS="-bios $(guix build ovmf)/share/firmware/ovmf_x64.bin"

exec qemu-system-x86_64 -enable-kvm -hda /tmp/t.img -cdrom "$ISO" -m 1024 -boot d -net user -net nic,model=virtio -no-reboot $EFI_OPTS
P
P
pelzflorian (Florian Pelz) wrote on 20 May 2019 22:02
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 35806@debbugs.gnu.org)
20190520200251.34xfc6ik53hr6z5k@pelzflorian.localdomain
On Mon, May 20, 2019 at 05:01:40PM +0200, Ludovic Courtès wrote:
Toggle quote (10 lines)
> Hi!
>
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>
> > on a system newly installed from the 1.0.1 ISO image — on only some
> > reinstalls. Maybe it was my fault, but maybe not, it is kind of
> > spooky. Can others reproduce?
>
> No. (I did many installs in VMs before the release… :-))

OK. I consider it likely that a typo was the reason for the wrong
password on the first install.

However, the second install had no normal user account, as you can see
in my /etc/shadow (which is attached again). It should not have been
possible to install without user account. Now that I think about it,
I believe when I got shown the user account creation page in the
installer, I accidentally immediately pressed some key (maybe Enter)
and it threw me back to the locale selection. I configured everything
again, but I believe this was the reason no user account was created.

I could now make the user account creation page crash again by
entering a wrong password confirmation, but after going through the
installer again, the resulting config contains a user and I can login.
I do not know how I managed to break this.

Toggle quote (5 lines)
>
> Note that you can check by doing an install in a VM using the attached
> script.
>

Thank you. For now I’ll try on real hardware though.

Regards,
Florian
root:$6$vWBy92HZjt$P.g83qzyyuZ0AebfKjsS/gZV.1SlaMkUqsmsO9cP1yXtpsCIE.9gDNDtMVwZWa..wmvVNqjqgjg7OFhKadshF.:18036::::::
nobody:!:18036::::::
guixbuilder01:!:18036::::::
guixbuilder02:!:18036::::::
guixbuilder03:!:18036::::::
guixbuilder04:!:18036::::::
guixbuilder05:!:18036::::::
guixbuilder06:!:18036::::::
guixbuilder07:!:18036::::::
guixbuilder08:!:18036::::::
guixbuilder09:!:18036::::::
guixbuilder10:!:18036::::::
messagebus:!:18036::::::
polkitd:!:18036::::::
L
L
Ludovic Courtès wrote on 20 May 2019 22:36
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(address . 35806@debbugs.gnu.org)
87imu4q2wf.fsf@gnu.org
Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

Toggle quote (13 lines)
> However, the second install had no normal user account, as you can see
> in my /etc/shadow (which is attached again). It should not have been
> possible to install without user account. Now that I think about it,
> I believe when I got shown the user account creation page in the
> installer, I accidentally immediately pressed some key (maybe Enter)
> and it threw me back to the locale selection. I configured everything
> again, but I believe this was the reason no user account was created.
>
> I could now make the user account creation page crash again by
> entering a wrong password confirmation, but after going through the
> installer again, the resulting config contains a user and I can login.
> I do not know how I managed to break this.

Could you file a bug specifically for this one if you managed to
reproduce it?

Toggle quote (6 lines)
>> Note that you can check by doing an install in a VM using the attached
>> script.
>>
>
> Thank you. For now I’ll try on real hardware though.

Well that’s even better. :-)

Should we consider this bug closed?

Thanks,
Ludo’.
P
P
pelzflorian (Florian Pelz) wrote on 20 May 2019 22:41
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 35806@debbugs.gnu.org)
20190520204133.hf6oihw2k3zcycwk@pelzflorian.localdomain
On Mon, May 20, 2019 at 10:36:32PM +0200, Ludovic Courtès wrote:
Toggle quote (21 lines)
> Hi,
>
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>
> > However, the second install had no normal user account, as you can see
> > in my /etc/shadow (which is attached again). It should not have been
> > possible to install without user account. Now that I think about it,
> > I believe when I got shown the user account creation page in the
> > installer, I accidentally immediately pressed some key (maybe Enter)
> > and it threw me back to the locale selection. I configured everything
> > again, but I believe this was the reason no user account was created.
> >
> > I could now make the user account creation page crash again by
> > entering a wrong password confirmation, but after going through the
> > installer again, the resulting config contains a user and I can login.
> > I do not know how I managed to break this.
>
> Could you file a bug specifically for this one if you managed to
> reproduce it?
>

I will try and then file a more specific bug.

Toggle quote (11 lines)
> >> Note that you can check by doing an install in a VM using the attached
> >> script.
> >>
> >
> > Thank you. For now I’ll try on real hardware though.
>
> Well that’s even better. :-)
>
> Should we consider this bug closed?
>

Yes.

Regards,
Florian
L
L
Ludovic Courtès wrote on 21 May 2019 10:09
control message for bug #35806
(address . control@debbugs.gnu.org)
87k1ek6xga.fsf@gnu.org
tags 35806 notabug
close 35806
A
A
Andreas Enge wrote on 27 May 2019 12:03
Re: bug#35806: Login passwords incorrect on some newly installed 1.0.1 systems
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)
20190527100342.GA5609@jurong
So closing it by cc-ing 35806-done@debbugs.gnu.org.

Andreas
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 35806@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 35806
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch