From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Cc: Clemens Gruber <clemens.gruber@pqgruber.com>
Subject: [ptxdist] [PATCH 1/2] file: seccomp sandboxing
Date: Wed, 27 Jun 2018 17:24:08 +0200 [thread overview]
Message-ID: <20180627152409.29979-1-clemens.gruber@pqgruber.com> (raw)
Support seccomp sandboxing to reduce the attack surface and enable it by
default. Important for usecases with files from untrusted sources.
Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>
---
rules/file.in | 14 +++++++++++++-
rules/file.make | 2 +-
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/rules/file.in b/rules/file.in
index a4e0a7125..3f44cc380 100644
--- a/rules/file.in
+++ b/rules/file.in
@@ -1,10 +1,11 @@
## SECTION=shell_and_console
-config FILE
+menuconfig FILE
tristate
select HOST_FILE
select ZLIB
select GCCLIBS_GCC_S
+ select LIBSECCOMP if FILE_SECCOMP
prompt "file"
help
The file command is "a file type guesser", that is, a command-line tool
@@ -15,3 +16,14 @@ config FILE
reliable, but requires a bit of I/O.
http://www.darwinsys.com/file/
+
+if FILE
+
+config FILE_SECCOMP
+ bool
+ default y
+ prompt "enable seccomp sandboxing"
+ help
+ Enables seccomp sandboxing to reduce the attack surface.
+
+endif
diff --git a/rules/file.make b/rules/file.make
index d60a0b045..bfa39ae76 100644
--- a/rules/file.make
+++ b/rules/file.make
@@ -37,7 +37,7 @@ FILE_CONF_OPT := \
--enable-elf \
--enable-elf-core \
--enable-zlib \
- --disable-libseccomp \
+ --$(call ptx/endis, PTXCONF_FILE_SECCOMP)-libseccomp \
--disable-fsect-man5 \
$(GLOBAL_LARGE_FILE_OPTION) \
--disable-warnings
--
2.18.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2018-06-27 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 15:24 Clemens Gruber [this message]
2018-06-27 15:24 ` [ptxdist] [PATCH 2/2] file: add upstream seccomp patches Clemens Gruber
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=20180627152409.29979-1-clemens.gruber@pqgruber.com \
--to=clemens.gruber@pqgruber.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