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: Dmitry Kasatkin <dmitry.kasatkin@huawei.com>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>,
	Mikhail Kurinnoi <viewizard@viewizard.com>
Subject: Re: [RFC] EVM: Add support for portable signature format
Date: Wed, 01 Nov 2017 14:25:04 -0400	[thread overview]
Message-ID: <1509560704.3583.322.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACdnJuuDpVSoGHcqjU-=z0nY_e7paQ0u4efD-1DBeTbADbB4iA@mail.gmail.com>

On Wed, 2017-11-01 at 10:54 -0700, Matthew Garrett wrote:
> Ok, thinking about this some more, I think I'm conflating two
> independent things here. Whether the extended attributes and file
> contents are modifiable is a matter of policy rather than something
> that should be tied to the signature format, so I think the approach
> that makes sense is to make the portable signatures immutable (as
> previously discussed)

So updating any file metadata, including security xattrs, included in
the signature will not cause the security.evm to change.  The file
metadata will be permited to change.

> and then allow userland to define a policy that
> permits modification of the protected metadata. I'll split this up and
> retest.

This subsequent patch will define a method for preventing the file
metadata included in the signature from changing as well.

Where is this policy?  Do you mean a build or runtime configuration?

      reply	other threads:[~2017-11-01 18:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26  8:31 [RFC] EVM: Add support for portable signature format Matthew Garrett
2017-10-26  9:03 ` Mikhail Kurinnoi
2017-10-26  9:08   ` Matthew Garrett
2017-10-26  9:46     ` Mikhail Kurinnoi
2017-10-26 19:22       ` Mimi Zohar
2017-10-30 10:53         ` Matthew Garrett
2017-10-30 11:36           ` Mimi Zohar
2017-10-30 11:51             ` Matthew Garrett
2017-10-30 12:14               ` Mimi Zohar
2017-10-27 10:27 ` Dmitry Kasatkin
2017-10-30 12:30   ` Mimi Zohar
2017-10-30 13:21     ` Matthew Garrett
2017-10-30 13:58       ` Mimi Zohar
2017-10-30 14:04         ` Matthew Garrett
2017-10-27 10:41 ` Dmitry Kasatkin
2017-10-30 12:38   ` Mimi Zohar
2017-10-30 13:17     ` Matthew Garrett
2017-10-30 15:31       ` Mimi Zohar
2017-10-30 15:36         ` Matthew Garrett
2017-11-01 17:54           ` Matthew Garrett
2017-11-01 18:25             ` 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=1509560704.3583.322.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=dmitry.kasatkin@huawei.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.com \
    --cc=viewizard@viewizard.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.