linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@google.com>
To: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>
Subject: Re: Writing out EVM protected xattrs while EVM is active
Date: Thu, 19 Oct 2017 10:06:13 -0700	[thread overview]
Message-ID: <CACdnJus81i3RZJQHwcdQMy3HX3KDQTYbQCCGQXaVqNs3ADrd5Q@mail.gmail.com> (raw)
In-Reply-To: <CACE9dm_ijBqhyQOPmWYXq+uzJ2Cxi1J92QDuqketrF6HKfH8BA@mail.gmail.com>

On Thu, Oct 19, 2017 at 4:00 AM, Dmitry Kasatkin
<dmitry.kasatkin@gmail.com> wrote:
> On Wed, Oct 18, 2017 at 2:12 AM, Matthew Garrett <mjg59@google.com> wrote:
>> I'm interested in extending our use of IMA digital signatures to EVM
>> in order to protect security.capability (and, in the near future,
>> security.apparmor). However, right now this doesn't seem to quite work
>> in terms of allowing updates to a running system. We've discussed the
>> EVM siganture format's use of inode numbers and I think I've got that
>> sorted (I'll send a patch once I've got a last couple of things
>> working).
>>
>> However, I'm a little confused by how EVM should be working here. Once
>> EVM is initialised, all EVM attributes will be protected, making it
>> impossible to write new values to any xattrs covered by EVM unless
>> IMA_NEW_FILE is set.
>
>
> Sorry, why it is not possible to set xattrs?
> system can change xattrs and hmac will be recalculated...

Because there's no symmetric key loaded in this case.

      reply	other threads:[~2017-10-19 17:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 23:12 Writing out EVM protected xattrs while EVM is active Matthew Garrett
2017-10-18  1:49 ` Mimi Zohar
2017-10-18  2:02   ` Matthew Garrett
2017-10-18  2:08     ` Mimi Zohar
2017-10-18  2:13       ` Matthew Garrett
2017-10-18  2:53         ` Mimi Zohar
2017-10-18 17:27           ` Matthew Garrett
2017-10-18 17:51             ` Mimi Zohar
2017-10-18 18:08               ` Matthew Garrett
2017-10-18 18:19                 ` Mimi Zohar
2017-10-18 18:23                   ` Matthew Garrett
2017-10-18 18:38                     ` Mimi Zohar
     [not found]               ` <CACE9dm_vpTi705PJxGZkeNWUyHALZzVc2x=RUw_p=DZCPZfoXw@mail.gmail.com>
2017-10-18 18:18                 ` Matthew Garrett
2017-10-19 11:14                   ` Dmitry Kasatkin
2017-10-18 18:19                 ` Dmitry Kasatkin
2017-10-19 11:00 ` Dmitry Kasatkin
2017-10-19 17:06   ` Matthew Garrett [this message]

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=CACdnJus81i3RZJQHwcdQMy3HX3KDQTYbQCCGQXaVqNs3ADrd5Q@mail.gmail.com \
    --to=mjg59@google.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=zohar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).