From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12046] Can’t login as root user after upgrading to buildroot 2019.02
Date: Sat, 27 Jul 2019 06:38:24 +0000 [thread overview]
Message-ID: <bug-12046-163-Y4fNBXhQVp@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12046-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12046
--- Comment #3 from liadekel123 at gmail.com ---
Hey Carlos,
Sorry about the delay. We solved the problem...
Apparently the version of login in buildroot 2019.02 use securetty file which
lists all the devices root user is allowed to login from :|
Many Thanks,
Liad
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-27 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 17:49 [Buildroot] [Bug 12046] New: Can’t login as root user after upgrading to buildroot 2019.02 bugzilla at busybox.net
2019-07-18 18:56 ` [Buildroot] [Bug 12046] " bugzilla at busybox.net
2019-07-27 0:07 ` bugzilla at busybox.net
2019-07-27 6:38 ` bugzilla at busybox.net [this message]
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-Y4fNBXhQVp@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