From: Richard Weinberger <richard@nod.at>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Nicholas Piggin <npiggin@gmail.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
david@sigma-star.at, kbuild-all@01.org,
Sam Ravnborg <sam@ravnborg.org>,
Arnaud Lacombe <lacombar@gmail.com>,
Nick Bowler <nbowler@elliptictech.com>,
Michal Marek <mmarek@suse.cz>, Nicolas Pitre <nico@linaro.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH v2] kbuild: Don't source kernel config
Date: Tue, 20 Feb 2018 17:16:07 +0100 [thread overview]
Message-ID: <1919455.eZKeABUfgV@blindfold> (raw)
In-Reply-To: <CAK7LNAQT8jEHt39xG7BvMMWjObdvCCpPhJAA83LFut4ewUVQsg@mail.gmail.com>
Am Dienstag, 20. Februar 2018, 17:00:39 CET schrieb Masahiro Yamada:
> 2018-02-21 0:25 GMT+09:00 Richard Weinberger <richard@nod.at>:
> > Am Dienstag, 20. Februar 2018, 16:18:11 CET schrieb Masahiro Yamada:
> >> 2018-02-19 18:22 GMT+09:00 Richard Weinberger <richard@nod.at>:
> >> > Don't source the kernel config file in shell scripts.
> >> > The config file is not a shell script and often imported from untrusted
> >> > sources.
> >> > What could possible go wrong? ;-)
> >>
> >> Please enumerate your real problems.
> >
> > Build a kernel where the .config contains something like:
> > CONFIG_CMDLINE_BOOL=y
> > CONFIG_CMDLINE="`echo hello > world`"
>
> Same for Makefile
> if a string symbol is referenced from Makefile, like
>
> CONFIG_CROSS_COMPILE="$(shell echo hello > world)aarch64-linux-gnu-"
Correct. But you forget that the .config file is often imported from untrusted
sources. Like on LKML, "my kernel explodes, this is the .config".
Jonny random Kernel developer then takes the .config and builds it...
> > I'll send a v3 because I forgot to convert one function in the shell
> > script to the new bash array. kbuild bot FTW. :-)
>
> You do not need to do so.
Okay, let's wait until toxic .configs appear in the wild. ;-)
> This patch is so ugly.
>
> Also, changed shell scripts have '#!/bin/sh' shebang,
> but you are adding bash as a requirement.
An alternate approach would be this:
diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
index 5c12dc91ef34..ff0a7c62344b 100644
--- a/scripts/kconfig/confdata.c
+++ b/scripts/kconfig/confdata.c
@@ -161,6 +161,13 @@ static int conf_set_sym_val(struct symbol *sym, int def,
int def_flags, char *p)
case S_STRING:
if (*p++ != '"')
break;
+
+ p2 = strpbrk(p, "`$");
+ if (p2 && !(p2[0] == '$' && p2[1] != '(')) {
+ conf_warning("string contains forbidden characters");
+ return 1;
+ }
+
for (p2 = p; (p2 = strpbrk(p2, "\"\\")); p2++) {
if (*p2 == '"') {
*p2 = 0;
That way the conf tool will sanitize the .config before shell scripts will
source it.
Thanks,
//richard
next prev parent reply other threads:[~2018-02-20 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 9:22 [PATCH v2] kbuild: Don't source kernel config Richard Weinberger
2018-02-20 15:18 ` Masahiro Yamada
2018-02-20 15:25 ` Richard Weinberger
2018-02-20 16:00 ` Masahiro Yamada
2018-02-20 16:16 ` Richard Weinberger [this message]
2018-02-20 16:26 ` Nicolas Pitre
2018-02-20 16:30 ` Masahiro Yamada
2018-02-20 16:55 ` Richard Weinberger
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=1919455.eZKeABUfgV@blindfold \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=david@sigma-star.at \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nbowler@elliptictech.com \
--cc=nico@linaro.org \
--cc=npiggin@gmail.com \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=yamada.masahiro@socionext.com \
/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;
as well as URLs for NNTP newsgroup(s).