From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12046] New: Can’t login as root user after upgrading to buildroot 2019.02
Date: Thu, 18 Jul 2019 17:49:54 +0000 [thread overview]
Message-ID: <bug-12046-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12046
Bug ID: 12046
Summary: Can?t login as root user after upgrading to buildroot
2019.02
Product: buildroot
Version: 2019.02
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: liadekel123 at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Hi everyone,
2 weeks ago we upgraded our buildroot version from 2018.03 to 2019.02 .
Until now we were using getty in order to login, and enabled login with
root user on our defconfig.
After upgrading as described above, we can?t login with root user,
While with standard user we do succeed.
As I saw one of the changes between the versions was that md5 is no longer
supported to hash the shadow file (same shadow file which contains our standard
user details).
We did tried to change the root password without any further success.
I?ll appreciate any ideas ...
Many Thanks (:
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-07-18 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 17:49 bugzilla at busybox.net [this message]
2019-07-18 18:56 ` [Buildroot] [Bug 12046] Can’t login as root user after upgrading to buildroot 2019.02 bugzilla at busybox.net
2019-07-27 0:07 ` bugzilla at busybox.net
2019-07-27 6:38 ` bugzilla at busybox.net
2019-07-27 20:45 ` bugzilla at busybox.net
2019-07-28 13:50 ` bugzilla at busybox.net
2019-07-29 1:35 ` bugzilla at busybox.net
2019-07-29 4:24 ` bugzilla at busybox.net
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=bug-12046-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox