All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Matthew Garrett <mjg59@google.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: [PATCH V4 2/2] EVM: Allow runtime modification of the set of verified xattrs
Date: Fri, 11 May 2018 16:05:44 -0400	[thread overview]
Message-ID: <1526069144.3559.9.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACdnJutj9oKqOX7UBXWbD+CpdL3Ed77=evN1gutRsZK1VWtYzQ@mail.gmail.com>

On Fri, 2018-05-11 at 12:51 -0700, Matthew Garrett wrote:

> > Should "evm_xattrs" be defined directly in the securityfs directory or
> > in a subdirectory similar to ima?  It will be difficult later on to
> > move "evm_xattrs" to a subdirectory once applications start
> > reading/writing to it.  What would the subdirectory be called?
> 
> Yeah, that's tricky - the obvious directory would be evm, but that's
> already in use. integrity makes sense, but then ima should also be under it.

I haven't tried, but maybe we could use softlinks (eg.
<securityfs>/ima ==> <securityfs>/integrity/ima)?

And then there are namespaces ...

Mimi

  reply	other threads:[~2018-05-11 20:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 20:28 [PATCH V4 1/2] EVM: turn evm_config_xattrnames into a list Matthew Garrett
2018-05-09 20:28 ` [PATCH V4 2/2] EVM: Allow runtime modification of the set of verified xattrs Matthew Garrett
2018-05-10 18:14   ` James Morris
2018-05-11  4:41   ` Mimi Zohar
2018-05-11 19:51     ` Matthew Garrett
2018-05-11 20:05       ` Mimi Zohar [this message]
2018-05-11 16:58   ` Mimi Zohar
2018-05-10 18:13 ` [PATCH V4 1/2] EVM: turn evm_config_xattrnames into a list James Morris
2018-05-11  4:03 ` 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=1526069144.3559.9.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.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.