linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: John Johansen <john.johansen@canonical.com>,
	Matthew Garrett <mjg59@google.com>,
	linux-integrity@vger.kernel.org
Subject: Re: [PATCH] EVM: Include security.apparmor in EVM measurements
Date: Sun, 15 Oct 2017 10:28:07 -0400	[thread overview]
Message-ID: <1508077687.3426.144.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <eaabb1e3-4cfe-653b-a1a8-8dabd5f24e06@canonical.com>

On Fri, 2017-10-13 at 16:36 -0700, John Johansen wrote:
> On 10/13/2017 03:09 PM, Matthew Garrett wrote:
> > Apparmor will be gaining support for security.apparmor labels, and it
> > would be helpful to include these in EVM validation now so appropriate
> > signatures can be generated even before full support is merged.
> > 
> > Signed-off-by: Matthew Garrett <mjg59@google.com>
> Acked-by: John Johansen <John.johansen@canonical.com>

Thanks!

> 
> > ---
> >  include/uapi/linux/xattr.h        | 3 +++
> >  security/integrity/evm/evm_main.c | 3 +++
> >  2 files changed, 6 insertions(+)
> > 
> > diff --git a/include/uapi/linux/xattr.h b/include/uapi/linux/xattr.h
> > index 1590c49cae57..e630b9cd70cb 100644
> > --- a/include/uapi/linux/xattr.h
> > +++ b/include/uapi/linux/xattr.h
> > @@ -65,6 +65,9 @@
> >  #define XATTR_NAME_SMACKTRANSMUTE XATTR_SECURITY_PREFIX XATTR_SMACK_TRANSMUTE
> >  #define XATTR_NAME_SMACKMMAP XATTR_SECURITY_PREFIX XATTR_SMACK_MMAP
> >  
> > +#define XATTR_APPARMOR_SUFFIX "apparmor"
> > +#define XATTR_NAME_APPARMOR XATTR_SECURITY_PREFIX XATTR_APPARMOR_SUFFIX
> > +
> >  #define XATTR_CAPS_SUFFIX "capability"
> >  #define XATTR_NAME_CAPS XATTR_SECURITY_PREFIX XATTR_CAPS_SUFFIX
> >  
> > diff --git a/security/integrity/evm/evm_main.c b/security/integrity/evm/evm_main.c
> > index 40bf3a20605d..78a5b1fddfc7 100644
> > --- a/security/integrity/evm/evm_main.c
> > +++ b/security/integrity/evm/evm_main.c
> > @@ -49,6 +49,9 @@ char *evm_config_xattrnames[] = {
> >  	XATTR_NAME_SMACKMMAP,
> >  #endif
> >  #endif
> > +#ifdef CONFIG_SECURITY_APPARMOR
> > +	XATTR_NAME_APPARMOR,
> > +#endif
> >  #ifdef CONFIG_IMA_APPRAISE
> >  	XATTR_NAME_IMA,
> >  #endif
> > 
> 

      reply	other threads:[~2017-10-15 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 22:09 [PATCH] EVM: Include security.apparmor in EVM measurements Matthew Garrett
2017-10-13 23:36 ` John Johansen
2017-10-15 14:28   ` Mimi Zohar [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=1508077687.3426.144.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=john.johansen@canonical.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 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).