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: Mon, 29 Jul 2019 01:35:54 +0000 [thread overview]
Message-ID: <bug-12046-163-sKBKL8TOaR@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12046-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12046
Carlos Santos <unixmania@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NEEDINFO |INVALID
--- Comment #6 from Carlos Santos <unixmania@gmail.com> ---
(In reply to liadekel123 from comment #5)
OK, I was able to reproduce the problem with the following defconfig:
BR2_x86_64=y
BR2_DL_DIR="$(HOME)/src"
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="https://toolchains.bootlin.com/downloads/releases/toolchains/x86-64-core-i7/tarballs/x86-64-core-i7--glibc--bleeding-edge-2018.11-1.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_8=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_14=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_SYSTEM_DHCP="eth0"
BR2_SYSTEM_ENABLE_NLS=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.19.16"
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/x86_64/linux.config"
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
123456789012345678901234567890123456789012345678901234567890123456789012
The problem happens with Busybox login:
- If linux-pam is NOT selected
- If /etc/securetty does not exist root can log in without restrictions
- If /etc/securetty exists then root can log in only on terminals listed
there
- If linux-pam is selected
- If pam_securetty is NOT enabled in /etc/pam.d/login then /etc/securetty is
ignored
- If pam_securetty is enabled with "auth required pam_securetty.so"
- If /etc/securetty does not exist root can log in without restrictions
- If /etc/securetty exists then can log in only on terminals listed there
Considering that by default Buildroot does NOT install a /etc/securetty file
I'm keeping this bug as RESOLVED but changing the resolution reason from
NEEDINFO to INVALID.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-29 1:35 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
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 [this message]
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-sKBKL8TOaR@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