From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/bash: add /bin/bash to /etc/shells
Date: Sat, 3 Feb 2018 15:45:54 +0100 [thread overview]
Message-ID: <20180203144554.GA2369@scaer> (raw)
In-Reply-To: <8c2a6cb6-7993-b05f-144f-82986cf2b913@mind.be>
Arnout, All,
On 2018-01-18 00:53 +0100, Arnout Vandecappelle spake thusly:
> On 13-01-18 17:12, Yann E. MORIN wrote:
> > Romain, All,
> >
> > On 2018-01-13 17:05 +0100, Romain Naour spake thusly:
> >> When bash is selected, /bin/bash is not added to /etc/shells
> >> (see man shells). So, login tools like dropbear reject the ssh
> >> connexions for users using bash as shell in /etc/passwd.
> >>
> >> buildroot authpriv.warn dropbear[853]: User 'kubu' has invalid shell, rejected
> >>
> >> Reported-by: Jeremy Rosen <jeremy.rosen@smile.fr>
> >> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> >> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >
> > Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
> Really? The guy who wrote the script that checks that no two packages can touch
> the same file acks this change?
Yes, nobody's perfect, and I never claimed I was.
Oh, I forgot: ;-)
> [snip]
> >> + grep -qsE '^/bin/bash' $(TARGET_DIR)/etc/shells \
> >> + || echo "/bin/bash" >> $(TARGET_DIR)/etc/shells
>
> So this is a nice example of a package breaking top-level parallel build.
>
> I guess the solution is to collect the shells in a make variable and create
> /etc/shells in a finalize hook. Or alternatively, do this in a finalize hook
> instead of target-install hook.
Yeah, target-finalize hooks is way better, because that does not add any
infra; it just uses existign infra.
Regards,
Yann E. MORIN.
> Regards,
> Arnout
>
> --
> Arnout Vandecappelle arnout at mind be
> Senior Embedded Software Architect +32-16-286500
> Essensium/Mind http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-02-03 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 16:05 [Buildroot] [PATCH v2] package/bash: add /bin/bash to /etc/shells Romain Naour
2018-01-13 16:12 ` Yann E. MORIN
2018-01-17 23:53 ` Arnout Vandecappelle
2018-01-18 9:46 ` Romain Naour
2018-01-18 12:25 ` Arnout Vandecappelle
2018-01-18 14:04 ` Romain Naour
2018-02-03 14:45 ` Yann E. MORIN [this message]
2018-01-14 14:04 ` Thomas Petazzoni
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=20180203144554.GA2369@scaer \
--to=yann.morin.1998@free.fr \
--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