From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] chrony: fix runtime with busybox init
Date: Tue, 29 Jun 2021 07:09:22 +0200 [thread overview]
Message-ID: <20210629050922.2524242-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20210619152607.858107-1-bruno.thomsen@gmail.com>
Thanks, applied as e109b0935b4676f027714dbe59317185a9d602cd.
Michael
[sent from post-receive hook]
On Tue, 29 Jun 2021 07:09:22 +0200, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> Run as root if busybox init is used (INITMETHOD_BBINIT) so
> runtime directory is read and writable. When running under
> systemd (INITMETHOD_SYSTEMD) use chrony user.
>
> A busybox init system typically ends up with a turtle shell
> security architecture where systemd is used when defense in
> depth is needed.
>
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20210619152607.858107-1-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/chrony.make b/rules/chrony.make
> index 4435b8e97796..cbdf9314b52b 100644
> --- a/rules/chrony.make
> +++ b/rules/chrony.make
> @@ -54,7 +54,7 @@ CHRONY_CONF_OPT := \
> --disable-phc \
> $(call ptx/ifdef, PTXCONF_CHRONY_PPS_REFCLK,,--disable-pps) \
> $(call ptx/ifdef, PTXCONF_GLOBAL_IPV6,,--disable-ipv6) \
> - --with-user=chrony \
> + --with-user=$(call ptx/ifdef, PTXCONF_INITMETHOD_SYSTEMD,chrony,root) \
> $(call ptx/ifdef, PTXCONF_CHRONY_SECCOMP,--enable-scfilter,) \
> $(call ptx/ifdef, PTXCONF_CHRONY_SECCOMP,,--without-seccomp)
>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-06-29 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 15:26 [ptxdist] [PATCH] " Bruno Thomsen
2021-06-29 5:09 ` Michael Olbrich [this message]
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=20210629050922.2524242-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bruno.thomsen@gmail.com \
--cc=ptxdist@pengutronix.de \
/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