From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Matt Brown <matt@nmatt.com>, Kees Cook <keescook@chromium.org>
Cc: James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM
Date: Fri, 09 Jun 2017 06:18:27 -0400 [thread overview]
Message-ID: <1497003507.21594.177.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <94ba5ebb-952b-2037-799e-07306629a6f9@nmatt.com>
On Thu, 2017-06-08 at 23:50 -0400, Matt Brown wrote:
> >>
> >> * Issues:
> >> * Can be bypassed by interpreted languages such as python. You can run
> >> malicious code by doing: python -c 'evil code'
> >
> > What's the recommendation for people interested in using TPE but
> > having interpreters installed?
> >
>
> If you don't need a given interpreter installed, uninstall it. While
> this is common sense system hardening it especially would make a
> difference under the TPE threat model.
>
> I don't have a knock down answer for this. Interpreters are a hard
> problem for TPE.
You might be interested in the minor LSM named "shebang", that I
posted as a proof of concept back in January, which restricts the
python interactive prompt/interpreter, but allows the scripts
themselves to be executed.
Mimi
next prev parent reply other threads:[~2017-06-09 10:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 3:43 [PATCH v2 0/1] " Matt Brown
2017-06-08 3:43 ` [PATCH v2 1/1] " Matt Brown
2017-06-09 2:38 ` Kees Cook
2017-06-09 3:50 ` Matt Brown
2017-06-09 10:18 ` Mimi Zohar [this message]
2017-06-09 12:55 ` Kees Cook
2017-06-09 13:15 ` Matt Brown
2017-06-09 13:16 ` Mimi Zohar
2017-06-09 13:18 ` [kernel-hardening] " Matt Brown
2017-06-09 13:44 ` Mimi Zohar
2017-06-16 2:25 ` [RFC PATCH] print_tpe_error() can be static kbuild test robot
2017-06-16 2:25 ` [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM kbuild test robot
2017-06-08 18:37 ` [PATCH v2 0/1] " Alan Cox
2017-06-08 19:01 ` Matt Brown
2017-06-08 19:23 ` Alan Cox
2017-06-11 11:30 ` Mickaël Salaün
2017-06-12 0:04 ` Matt Brown
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=1497003507.21594.177.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=james.l.morris@oracle.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matt@nmatt.com \
--cc=serge@hallyn.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
all inboxes | Powered by JetHome®