From: James Morris <james.l.morris@oracle.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: Matthew Garrett <mjg59@google.com>,
linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: IMA appraisal master plan? (was: Re: [PATCH V6] EVM: Add support for portable signature format)
Date: Thu, 16 Nov 2017 11:02:30 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711161101360.27132@localhost> (raw)
In-Reply-To: <1510770065.5979.21.camel@intel.com>
On Wed, 15 Nov 2017, Patrick Ohly wrote:
> I have some experience with SMACK, but not with Apparmor. At least with
> SMACK the problem is that the LSM depends on integrity protection of
> the xattrs, but the integrity protection itself depends on the LSM, so
> there's a cycle. An attacker can much too easily make offline changes
> which then defeat whatever IMA policy the system might be using.
Isn't this what EVM is supposed to mitigate?
Can you explain the offline attack in this scenario?
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2017-11-16 0:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 15:17 [PATCH V6] EVM: Add support for portable signature format Matthew Garrett
2017-11-08 19:37 ` Mimi Zohar
2017-11-15 17:26 ` IMA appraisal master plan? (was: Re: [PATCH V6] EVM: Add support for portable signature format) Patrick Ohly
2017-11-15 17:58 ` Matthew Garrett
2017-11-15 18:21 ` Patrick Ohly
2017-11-15 18:28 ` Matthew Garrett
2017-11-16 0:02 ` James Morris [this message]
2017-11-16 0:05 ` Matthew Garrett
2017-11-16 2:13 ` Mimi Zohar
2017-11-16 9:23 ` IMA appraisal master plan? Roberto Sassu
2017-11-16 10:20 ` Patrick Ohly
2017-11-16 13:13 ` Mimi Zohar
2017-11-16 14:18 ` Roberto Sassu
2017-11-16 13:06 ` Mimi Zohar
2017-11-17 12:20 ` Roberto Sassu
2017-11-17 12:20 ` Roberto Sassu
2017-11-17 13:42 ` Mimi Zohar
2017-11-17 13:42 ` Mimi Zohar
2017-11-17 14:32 ` Roberto Sassu
2017-11-17 14:32 ` Roberto Sassu
2017-11-17 15:58 ` Stephen Smalley
2017-11-17 17:54 ` Stephen Smalley
2017-11-17 20:09 ` Safford, David (GE Global Research, US)
2017-11-18 19:29 ` Casey Schaufler
2017-11-19 20:47 ` James Morris
2017-11-19 20:47 ` James Morris
2017-11-20 10:20 ` Patrick Ohly
2017-11-20 10:20 ` Patrick Ohly
2017-11-20 14:59 ` Mimi Zohar
2017-11-20 14:59 ` Mimi Zohar
2017-11-20 16:15 ` Patrick Ohly
2017-11-20 16:15 ` Patrick Ohly
2017-11-21 10:05 ` James Morris
2017-11-21 10:05 ` James Morris
2017-11-21 9:33 ` Roberto Sassu
2017-11-21 9:33 ` Roberto Sassu
2017-11-21 14:05 ` Mimi Zohar
2017-11-21 14:05 ` Mimi Zohar
2017-11-21 15:25 ` Roberto Sassu
2017-11-21 15:25 ` Roberto Sassu
2017-11-21 15:53 ` Mimi Zohar
2017-11-21 15:53 ` Mimi Zohar
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=alpine.LFD.2.20.1711161101360.27132@localhost \
--to=james.l.morris@oracle.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
--cc=patrick.ohly@intel.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.