From: Solar Designer <solar@openwall.com>
To: Greg KH <greg@kroah.com>
Cc: Matt Brown <matt@nmatt.com>, kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] [PATCH v1 1/1] Add Trusted Path Execution as a stackable LSM
Date: Sat, 3 Jun 2017 18:22:31 +0200 [thread overview]
Message-ID: <20170603162231.GA20590@openwall.com> (raw)
In-Reply-To: <20170603155920.GA25740@kroah.com>
On Sat, Jun 03, 2017 at 05:59:20PM +0200, Greg KH wrote:
> But for those systems, and this feature as well, can't a "simple"
> apparmor policy do the exact same thing? Also, I'm sure the SELinux can
> do this as well, but I don't know the config language there as well.
>
> So I think this is already a feature that is supported, it just takes a
> bit more configuration work on the admin.
Yes, that's "a bit" more effort up to the point where almost(?) no one
would bother. Sometimes simple features can reasonably co-exist with
more general frameworks that could also be used to achieve the effect.
So I don't view this as a sufficiently good argument against TPE as a
feature on its own.
Alexander
next prev parent reply other threads:[~2017-06-03 16:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 5:53 [kernel-hardening] [PATCH v1 1/1] Add Trusted Path Execution as a stackable LSM Matt Brown
2017-06-03 5:53 ` Matt Brown
2017-06-03 5:53 ` Matt Brown
2017-06-03 6:33 ` [kernel-hardening] " Al Viro
2017-06-03 6:33 ` Al Viro
2017-06-03 6:33 ` Al Viro
2017-06-04 5:24 ` [kernel-hardening] " Matt Brown
2017-06-04 5:24 ` Matt Brown
2017-06-04 5:24 ` Matt Brown
2017-06-04 5:47 ` [kernel-hardening] " Eric Biggers
2017-06-04 5:47 ` Eric Biggers
2017-06-04 12:43 ` Matt Brown
2017-06-04 12:43 ` Matt Brown
2017-06-04 6:51 ` Al Viro
2017-06-04 6:51 ` Al Viro
2017-06-04 6:51 ` Al Viro
2017-06-03 10:39 ` [kernel-hardening] " Jann Horn
2017-06-03 10:39 ` Jann Horn
2017-06-03 22:30 ` Matt Brown
2017-06-03 22:30 ` Matt Brown
2017-06-03 15:47 ` Solar Designer
2017-06-03 15:59 ` Greg KH
2017-06-03 16:22 ` Solar Designer [this message]
2017-06-03 17:16 ` Daniel Micay
2017-06-03 22:02 ` Nicolas Belouin
2017-06-03 21:55 ` Corey Henderson
2017-06-03 16:13 ` Solar Designer
2017-06-05 14:41 ` Matt Brown
2017-06-05 15:23 ` Solar Designer
2017-06-04 16:43 ` Mickaël Salaün
2017-06-04 22:07 ` Mickaël Salaün
2017-06-05 15:30 ` [kernel-hardening] " Alan Cox
2017-06-05 15:30 ` Alan Cox
2017-06-05 15:30 ` Alan Cox
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=20170603162231.GA20590@openwall.com \
--to=solar@openwall.com \
--cc=greg@kroah.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=matt@nmatt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.