From: Luca Boccassi <Luca.Boccassi@microsoft.com>
To: "ebiggers@kernel.org" <ebiggers@kernel.org>,
"linux-fscrypt@vger.kernel.org" <linux-fscrypt@vger.kernel.org>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"victorhsieh@google.com" <victorhsieh@google.com>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>,
"maco@android.com" <maco@android.com>,
"paullawrence@google.com" <paullawrence@google.com>
Subject: Re: [PATCH 4/4] fs-verity: move structs needed for file signing to UAPI header
Date: Mon, 16 Nov 2020 11:25:11 +0000 [thread overview]
Message-ID: <1110494125be52ff267e3fb50d96756c04ac5ca5.camel@microsoft.com> (raw)
In-Reply-To: <20201113211918.71883-5-ebiggers@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On Fri, 2020-11-13 at 13:19 -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Although it isn't used directly by the ioctls,
> "struct fsverity_descriptor" is required by userspace programs that need
> to compute fs-verity file digests in a standalone way. Therefore
> it's also needed to sign files in a standalone way.
>
> Similarly, "struct fsverity_formatted_digest" (previously called
> "struct fsverity_signed_digest" which was misleading) is also needed to
> sign files if the built-in signature verification is being used.
>
> Therefore, move these structs to the UAPI header.
>
> While doing this, try to make it clear that the signature-related fields
> in fsverity_descriptor aren't used in the file digest computation.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> Documentation/filesystems/fsverity.rst | 6 +---
> fs/verity/fsverity_private.h | 37 -------------------
> include/uapi/linux/fsverity.h | 49 ++++++++++++++++++++++++++
> 3 files changed, 50 insertions(+), 42 deletions(-)
Acked-by: Luca Boccassi <luca.boccassi@microsoft.com>
--
Kind regards,
Luca Boccassi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2020-11-16 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 21:19 [PATCH 0/4] fs-verity cleanups Eric Biggers
2020-11-13 21:19 ` [PATCH 1/4] fs-verity: remove filenames from file comments Eric Biggers
2020-11-16 11:21 ` Luca Boccassi
2020-11-13 21:19 ` [PATCH 2/4] fs-verity: rename fsverity_signed_digest to fsverity_formatted_digest Eric Biggers
2020-11-13 21:19 ` [PATCH 3/4] fs-verity: rename "file measurement" to "file digest" Eric Biggers
2020-11-16 11:21 ` Luca Boccassi
2020-11-13 21:19 ` [PATCH 4/4] fs-verity: move structs needed for file signing to UAPI header Eric Biggers
2020-11-16 11:25 ` Luca Boccassi [this message]
2020-11-16 19:57 ` [PATCH 0/4] fs-verity cleanups Eric Biggers
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=1110494125be52ff267e3fb50d96756c04ac5ca5.camel@microsoft.com \
--to=luca.boccassi@microsoft.com \
--cc=Jes.Sorensen@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=maco@android.com \
--cc=paullawrence@google.com \
--cc=victorhsieh@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