Linux NFS development
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Cc: linux-fscrypt@vger.kernel.org, linux-integrity@vger.kernel.org,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: IMA metadata format to support fs-verity
Date: Wed, 26 Aug 2020 20:50:59 -0400	[thread overview]
Message-ID: <d565406cd0ae2d1649c0979a5f8445df2ae8ca41.camel@linux.ibm.com> (raw)
In-Reply-To: <20200826192403.GD2239109@gmail.com>

On Wed, 2020-08-26 at 12:24 -0700, Eric Biggers wrote:

> fs-verity is mostly just a way of hashing a file.  Can't IMA just continue to do
> its signatures in the same way, and just swap out the traditional full file hash
> with the fs-verity file hash (when it's enabled)?

Yes, as previously discussed with you and Ted.

Mimi
> 
> fs-verity does support its own signature mechanism, because people wanted a
> simple knob to set that makes the kernel verify and enforce signatures for all
> fs-verity files.  But it's not mandatory to use that.


      parent reply	other threads:[~2020-08-27  0:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 17:13 IMA metadata format to support fs-verity Chuck Lever
2020-08-26 18:31 ` Eric Biggers
2020-08-26 18:56   ` Chuck Lever
2020-08-26 19:24     ` Eric Biggers
2020-08-26 19:51       ` Chuck Lever
2020-08-26 20:51         ` Eric Biggers
2020-08-27  0:53           ` Mimi Zohar
2020-08-27  1:00             ` Eric Biggers
2020-08-27 13:10               ` Mimi Zohar
2020-08-27  0:50       ` 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=d565406cd0ae2d1649c0979a5f8445df2ae8ca41.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=chuck.lever@oracle.com \
    --cc=ebiggers@kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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