From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10896] New: /bin/sh not in /etc/shells
Date: Wed, 28 Mar 2018 13:11:32 +0000 [thread overview]
Message-ID: <bug-10896-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10896
Bug ID: 10896
Summary: /bin/sh not in /etc/shells
Product: buildroot
Version: 2018.02
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: posted at heine.so
CC: buildroot at uclibc.org
Target Milestone: ---
Hi,
I just updated my buildroot build from 2017.11 to 2018.02.
It broke my root ssh login.
I see the following message in my journal:
dropbear[383]: User 'root' has invalid shell, rejected
In 2017.11 there was no /etc/shells. Now there is one.
My /etc/shells contains only /bin/bash. But not /bin/sh. But my root users has
/bin/sh as shell, so the error makes sense.
Some quick comparison shows that the file /etc/shells was added in this commit:
4d279697afbf8fb2952 package/bash: add /bin/bash to /etc/shells
I see on the mailing list Romain Naour posted a series of commits which would
also add /bin/sh to shells in the skeleton-init-common. But this is still not
applied.
So I would suggest to either apply the patch series for the next maintenance
release or remove the before mentioned commit.
Regards,
Michael
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-03-28 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 13:11 bugzilla at busybox.net [this message]
2018-04-17 10:03 ` [Buildroot] [Bug 10896] /bin/sh not in /etc/shells bugzilla at busybox.net
2018-05-08 13:03 ` 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-10896-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