From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: Luca Boccassi <luca.boccassi@gmail.com>,
Jes Sorensen <Jes.Sorensen@gmail.com>
Subject: [fsverity-utils PATCH 0/2] Add libfsverity_enable() API
Date: Fri, 13 Nov 2020 16:15:27 -0800 [thread overview]
Message-ID: <20201114001529.185751-1-ebiggers@kernel.org> (raw)
This patchset adds wrappers around FS_IOC_ENABLE_VERITY to the library
API, and makes the fsverity commands share code to parse the
libfsverity_merkle_tree_params.
This is my proposed alternative to Luca's patch
https://lkml.kernel.org/linux-fscrypt/20201113143527.1097499-1-luca.boccassi@gmail.com
Eric Biggers (2):
lib: add libfsverity_enable() and libfsverity_enable_with_sig()
programs/fsverity: share code to parse tree parameters
include/libfsverity.h | 36 ++++++++++++++++++++++++++++++++++
lib/enable.c | 45 +++++++++++++++++++++++++++++++++++++++++++
programs/cmd_digest.c | 31 ++++-------------------------
programs/cmd_enable.c | 34 ++++++++------------------------
programs/cmd_sign.c | 31 ++++-------------------------
programs/fsverity.c | 42 ++++++++++++++++++++++++++++++++++++----
programs/fsverity.h | 19 ++++++++++++++----
7 files changed, 150 insertions(+), 88 deletions(-)
create mode 100644 lib/enable.c
--
2.29.2
next reply other threads:[~2020-11-14 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 0:15 Eric Biggers [this message]
2020-11-14 0:15 ` [fsverity-utils PATCH 1/2] lib: add libfsverity_enable() and libfsverity_enable_with_sig() Eric Biggers
2020-11-16 11:52 ` Luca Boccassi
2020-11-16 17:41 ` Eric Biggers
2020-11-16 17:50 ` Luca Boccassi
2020-11-16 18:42 ` Eric Biggers
2020-11-16 19:28 ` Luca Boccassi
2020-11-14 0:15 ` [fsverity-utils PATCH 2/2] programs/fsverity: share code to parse tree parameters Eric Biggers
2020-11-16 11:32 ` Luca Boccassi
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=20201114001529.185751-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jes.Sorensen@gmail.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=luca.boccassi@gmail.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.