linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Matthew Garrett <mjg59@google.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Subject: Re: [RFC] kexec: Allow kexec_file() with appropriate IMA policy when locked down
Date: Thu, 14 Mar 2019 18:31:31 -0400	[thread overview]
Message-ID: <1552602691.8658.49.camel@linux.ibm.com> (raw)
In-Reply-To: <CACdnJuv=-Gr9Psd1ABZ=fW43-2FHcgEkG_iu0bY20Jx4Vro=mA@mail.gmail.com>

On Thu, 2019-03-14 at 14:08 -0700, Matthew Garrett wrote:
> On Wed, Mar 13, 2019 at 6:08 PM Mimi Zohar <zohar@linux.ibm.com> wrote:
> > The IMA hash and EVM hmac combination is fine for offline protection.
> > It's used for mutable files.  For immutable files, there must be
> > either an IMA or EVM signature.
> 
> Ok. Is the correct way to handle this to check that the file has a
> signature, or to extend IMA policy to allow it to provide a
> requirement that EVM verify a signature rather than an HMAC and have
> the arch policy set that?

I'm not sure what you mean by "check that the file has a signature".

EVM and IMA are separate subsystems with a defined interface for
interaction between them. evm_verifyxattr() isn't, but could be called
by LSMs.  So evm_verifyxattr() would need to be extended to return the
EVM xattr type.  The IMA policy could then require a specific evmxattr
type.  Possible.

Perhaps for now require IMA signatures and defer supporting EVM
signatures?

Mimi





  reply	other threads:[~2019-03-14 22:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 19:57 [RFC] kexec: Allow kexec_file() with appropriate IMA policy when locked down Matthew Garrett
2019-03-13 11:58 ` Mimi Zohar
2019-03-13 20:36   ` Matthew Garrett
2019-03-13 21:29     ` Mimi Zohar
2019-03-13 21:59       ` Matthew Garrett
2019-03-14  1:08         ` Mimi Zohar
2019-03-14 21:08           ` Matthew Garrett
2019-03-14 22:31             ` Mimi Zohar [this message]
2019-03-14 22:54               ` Matthew Garrett
2019-03-14 23:58                 ` Mimi Zohar
2019-03-15 22:03                   ` Matthew Garrett
2019-03-17 11:39                     ` Mimi Zohar
2019-03-18 19:51                       ` 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=1552602691.8658.49.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=dmitry.kasatkin@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 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).