All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikhail Kurinnoi <viewizard@viewizard.com>
To: Matthew Garrett <mjg59@google.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Dmitry Kasatkin <dmitry.kasatkin@huawei.com>
Subject: Re: [PATCH V3] EVM: Add support for portable signature format
Date: Wed, 25 Oct 2017 14:24:51 +0300	[thread overview]
Message-ID: <20171025142451.188a4ddd@totoro> (raw)
In-Reply-To: <CACdnJutDgEsffdChL6LCf_+O15cUzJA0gt7jr4eC-ivQn43F7w@mail.gmail.com>

? Wed, 25 Oct 2017 03:43:34 -0700
Matthew Garrett <mjg59@google.com> ?????:

> On Wed, Oct 25, 2017 at 3:13 AM, Mikhail Kurinnoi
> <viewizard@viewizard.com> wrote:
> > In case of IMA hash update we will forced to update EVM xattr from
> > ima_fix_xattr() with __vfs_setxattr_noperm(), this mean we will not
> > call evm_inode_setxattr(), but call evm_inode_post_setxattr().
> >
> > Dmitry's patch
> > https://sourceforge.net/p/linux-ima/mailman/message/32987311/
> > have work around for this issue. Since, in case we have immutable
> > EVM, we should prevent any file data changes (IMA hash update).  
> 
> Ah - does this need any more than adding EVM_XATTR_PORTABLE_DIGSIG to
> the check in ima_appraise_measurement()? I can't see any other way
> that we could get to ima_fix_xattr().

I think, Dmitry put code into process_measurement() just because we
already have "mask" here, so, we could check it in easy way.

In previous discussion, Mimi asked move all EVM-related stuff
connected to this check into EVM module, instead of IMA. Probably, this
mean we should use EVM API (evm_verifyxattr(), called from
ima_appraise_measurement()), that we already have in order to EVM<->IMA
communication.



-- 
Best regards,
Mikhail Kurinnoi

  reply	other threads:[~2017-10-25 11:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25  9:54 [PATCH V3] EVM: Add support for portable signature format Matthew Garrett
2017-10-25  9:56 ` James Morris
2017-10-25 10:13 ` Mikhail Kurinnoi
2017-10-25 10:43   ` Matthew Garrett
2017-10-25 11:24     ` Mikhail Kurinnoi [this message]
2017-10-25 11:42       ` Dmitry Kasatkin
2017-10-25 11:56 ` 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=20171025142451.188a4ddd@totoro \
    --to=viewizard@viewizard.com \
    --cc=dmitry.kasatkin@huawei.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.com \
    --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 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.