From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35806@debbugs.gnu.org
Subject: bug#35806: Login passwords incorrect on some newly installed 1.0.1 systems
Date: Mon, 20 May 2019 22:02:51 +0200 [thread overview]
Message-ID: <20190520200251.34xfc6ik53hr6z5k@pelzflorian.localdomain> (raw)
In-Reply-To: <87o93xrwyz.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
On Mon, May 20, 2019 at 05:01:40PM +0200, Ludovic Courtès wrote:
> 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.
>
> 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
[-- Attachment #2: shadow --]
[-- Type: text/plain, Size: 466 bytes --]
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::::::
next prev parent reply other threads:[~2019-05-20 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 9:38 bug#35806: Login passwords incorrect on some newly installed 1.0.1 systems pelzflorian (Florian Pelz)
2019-05-20 15:01 ` Ludovic Courtès
2019-05-20 20:02 ` pelzflorian (Florian Pelz) [this message]
2019-05-20 20:36 ` Ludovic Courtès
2019-05-20 20:41 ` pelzflorian (Florian Pelz)
2019-05-27 10:03 ` Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190520200251.34xfc6ik53hr6z5k@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35806@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.