From: Mimi Zohar <zohar@linux.ibm.com>
To: linux-integrity@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.ibm.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/5] ima: support fs-verity signatures stored as
Date: Thu, 2 Dec 2021 16:55:02 -0500 [thread overview]
Message-ID: <20211202215507.298415-1-zohar@linux.ibm.com> (raw)
Support for fs-verity file digests in IMA was discussed from the beginning,
prior to fs-verity being upstreamed[1,2]. This patch set adds signature
verification support based on the fs-verity file digest. Both the
file digest and the signature must be included in the IMA measurement list
in order to disambiguate the type of file digest.
[1] https://events19.linuxfoundation.org/wp-content/uploads/2017/11/fs-verify_Mike-Halcrow_Eric-Biggers.pdf
[2] Documentation/filesystems/fsverity.rst
Changelog v1:
- Updated both fsverity and IMA documentation.
- Addressed both Eric Bigger's and Lakshmi's comments.
Mimi Zohar (5):
fs-verity: define a function to return the integrity protected file
digest
ima: define a new signature type named IMA_VERITY_DIGSIG
ima: limit including fs-verity's file digest in measurement list
ima: support fs-verity file digest based signatures
fsverity: update the documentation
Documentation/filesystems/fsverity.rst | 22 ++++++----
Documentation/security/IMA-templates.rst | 9 +++-
fs/verity/Kconfig | 1 +
fs/verity/fsverity_private.h | 7 ---
fs/verity/measure.c | 49 +++++++++++++++++++++
include/linux/fsverity.h | 18 ++++++++
security/integrity/ima/ima.h | 3 +-
security/integrity/ima/ima_api.c | 23 +++++++++-
security/integrity/ima/ima_appraise.c | 52 ++++++++++++++++++++++-
security/integrity/ima/ima_main.c | 7 ++-
security/integrity/ima/ima_template_lib.c | 3 +-
security/integrity/integrity.h | 1 +
12 files changed, 172 insertions(+), 23 deletions(-)
--
2.27.0
next reply other threads:[~2021-12-02 21:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 21:55 Mimi Zohar [this message]
2021-12-02 21:55 ` [PATCH v1 1/5] fs-verity: define a function to return the integrity protected file digest Mimi Zohar
2021-12-02 22:15 ` Eric Biggers
2021-12-02 21:55 ` [PATCH v1 2/5] ima: define a new signature type named IMA_VERITY_DIGSIG Mimi Zohar
2021-12-02 21:55 ` [PATCH v1 3/5] ima: limit including fs-verity's file digest in measurement list Mimi Zohar
2021-12-02 22:22 ` Eric Biggers
2021-12-02 22:55 ` Mimi Zohar
2021-12-02 21:55 ` [PATCH v1 4/5] ima: support fs-verity file digest based signatures Mimi Zohar
2021-12-02 22:07 ` Eric Biggers
2021-12-02 22:13 ` Mimi Zohar
2021-12-02 22:18 ` Eric Biggers
2021-12-31 15:35 ` Mimi Zohar
2022-01-05 23:37 ` Eric Biggers
2022-01-09 20:45 ` Vitaly Chikunov
2022-01-09 21:07 ` Eric Biggers
2022-01-15 5:31 ` Vitaly Chikunov
2022-01-15 6:21 ` Eric Biggers
2022-01-16 3:31 ` Stefan Berger
2022-01-16 5:24 ` Stefan Berger
2022-01-19 0:49 ` Eric Biggers
2022-01-19 15:41 ` Stefan Berger
2022-01-16 17:01 ` Mimi Zohar
2022-01-19 0:39 ` Eric Biggers
2022-01-20 16:39 ` Mimi Zohar
2022-01-20 21:05 ` Eric Biggers
2021-12-02 21:55 ` [PATCH v1 5/5] fsverity: update the documentation Mimi Zohar
2021-12-02 22:09 ` 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=20211202215507.298415-1-zohar@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).