From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/wrapper: extend the list of unsafe paths
Date: Mon, 22 Jun 2020 22:40:22 +0200 [thread overview]
Message-ID: <20200622224022.4db35402@windsurf.home> (raw)
In-Reply-To: <20200621203158.14520-1-yann.morin.1998@free.fr>
On Sun, 21 Jun 2020 22:31:58 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> On some legacy systems, the X11 headers and libs are in /usr/X11R66/include
> and /usr/X11R66/lib, and of course, some packages are trying to be smart
> and use those paths (even when they do not exist).
>
> Add those to the list of unsafe paths to check in the toolchain wrapper.
>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> toolchain/toolchain-wrapper.c | 2 ++
> 1 file changed, 2 insertions(+)
Applied to master, thanks. Do you remember why we don't simply
blacklist /usr entirely ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-22 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:31 [Buildroot] [PATCH] toolchain/wrapper: extend the list of unsafe paths Yann E. MORIN
2020-06-22 20:40 ` Thomas Petazzoni [this message]
2020-06-22 20:49 ` Yann E. MORIN
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=20200622224022.4db35402@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--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