From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v4] core/skeleton: drop /etc/securetty
Date: Mon, 13 Jul 2015 13:46:19 +0300 [thread overview]
Message-ID: <20150713104618.GO2451@tarshish> (raw)
In-Reply-To: <20150713103735.GI4008@free.fr>
Hi Yann,
On Mon, Jul 13, 2015 at 12:37:35PM +0200, Yann E. MORIN wrote:
> On 2015-07-13 12:44 +0300, Baruch Siach spake thusly:
> > It would still break overlays with /etc/securetty (maybe locally
> > modified). Why not just disable Busybox FEATURE_SECURETTY?
>
> After discussing this with Thomas, we've decided to keep it, especially
> to keep the case you mention (custom securetty from overlay) is still
> working as expected.
>
> The reasoning is that a user which installs a custom /etc/securetty will
> obviously have it contain the ttys he wants root to log in from, so he'd
> still be able to log in as root from those ttys.
>
> But if we were to remove FEATURE_SECURETTY, then he'd still be able to
> log in as root from those ttys, but *also* from *any other* tty, and
> would probably not notice that change as this is a silent change.
>
> So, we've concluded that we should keep FEATURE_SECURETTY since it works
> for our new use-case, and works for existing use-cases.
Makes sense. Thanks for the explanation.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-07-13 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 9:05 [Buildroot] [PATCH 0/2 v4] busybox: improve support for telnetd (branch yem/pw) Yann E. MORIN
2015-07-13 9:05 ` [Buildroot] [PATCH 1/2 v4] core/skeleton: drop /etc/securetty Yann E. MORIN
2015-07-13 9:20 ` Baruch Siach
2015-07-13 9:35 ` Yann E. MORIN
2015-07-13 9:44 ` Baruch Siach
2015-07-13 10:37 ` Yann E. MORIN
2015-07-13 10:46 ` Baruch Siach [this message]
2015-07-13 11:42 ` Arnout Vandecappelle
2015-07-13 9:05 ` [Buildroot] [PATCH 2/2 v4] busybox: improve support for telnetd Yann E. MORIN
2015-07-13 11:02 ` [Buildroot] [PATCH 0/2 v4] busybox: improve support for telnetd (branch yem/pw) 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=20150713104618.GO2451@tarshish \
--to=baruch@tkos.co.il \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.