From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Matthew Garrett <mjg59@google.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
Igor Stoppa <igor.stoppa@gmail.com>
Subject: Re: [PATCH] EVM: Allow runtime modification of the set of verified xattrs
Date: Wed, 25 Apr 2018 10:51:32 -0400 [thread overview]
Message-ID: <1524667892.3371.67.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACdnJusixeW6LUhFzTEdLgQwRfxf9SXup3CwCAL+gXfA0PPO8g@mail.gmail.com>
[CC'ing Igor]
On Tue, 2018-04-24 at 20:03 +0000, Matthew Garrett wrote:
> On Mon, Apr 16, 2018 at 1:22 PM Matthew Garrett <mjg59@google.com> wrote:
> > I could go either way on this - I think that doing it on the command line
> > would satisfy all my use cases.
>
> Thinking about this some more - I think being able to do this at runtime is
> actually important. If we add an additional xattr to the signatures then we
> want to be able to update machine policy without forcing a reboot first,
> otherwise we have a chicken and egg problem where we have to gate any new
> package update against having a machine rebooted with an updated command
> line (otherwise the signature validation will fail for packages that
> contain new signatures)
If the list of xattr names is append only, there is no reason for re-
allocating the entire xattr name list each time. As long as the xattr
name list pointer is defined as __ro_after_init, we can work with Igor
on using "protectable memory" once it is upstreamed.
Mimi
next prev parent reply other threads:[~2018-04-25 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 22:52 [PATCH] EVM: Allow runtime modification of the set of verified xattrs Matthew Garrett
2018-04-15 14:05 ` Mimi Zohar
2018-04-16 18:32 ` Matthew Garrett
2018-04-16 20:16 ` Mimi Zohar
2018-04-16 20:22 ` Matthew Garrett
2018-04-24 20:03 ` Matthew Garrett
2018-04-25 14:51 ` Mimi Zohar [this message]
2018-04-25 16:54 ` Matthew Garrett
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=1524667892.3371.67.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=igor.stoppa@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.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.