New: /bin/sh not in /etc/shells

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.

https://bugs.busybox.net/show_bug.cgi?id=10896

--- Comment #1 from Arnout Vandecappelle <[email protected]> --- Still present in 2018.02.1...

For 2018.02.x, I think it should be fixed by reverting the commit:
http://patchwork.ozlabs.org/patch/899178/

For master, the series should be applied:
http://patchwork.ozlabs.org/project/buildroot/list/?series=24357

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10896

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Thomas Petazzoni <[email protected]> --- In the 2018.02.x branch, we reverted the patch pointed by Arnout. For the master branch, and upcoming 2018.05, we also applied the series pointed by Arnout. Hence this bug is fixed. Thanks!

You are receiving this mail because:
You are on the CC list for the bug.