From: Luca Boccassi <bluca@debian.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-integrity@vger.kernel.org,
Jes Sorensen <jsorensen@meta.com>,
Victor Hsieh <victorhsieh@google.com>
Subject: Re: [PATCH] fsverity: mark builtin signatures as deprecated
Date: Sat, 17 Dec 2022 02:04:02 +0000 [thread overview]
Message-ID: <CAMw=ZnQNJjKVAf9xafashv8diab2Xg92M1+wNT3A37RMBVwR2Q@mail.gmail.com> (raw)
In-Reply-To: <Y5zbNtaadNGPGHQb@sol.localdomain>
On Fri, 16 Dec 2022 at 20:55, Eric Biggers <ebiggers@kernel.org> wrote:
>
> On Thu, Dec 08, 2022 at 09:37:29PM +0000, Luca Boccassi wrote:
> >
> > The second question is easy: because the kernel is the right place for
> > our use case to do this verification and enforcement, exactly like dm-
> > verity does.
>
> Well, dm-verity's in-kernel signature verification support is a fairly new
> feature. Most users of dm-verity don't use it, and will not be using it.
I'm not sure what you mean by "most users" - systemd has support for
dm-verity signatures all over the place, libcryptsetup/veritysetup
supports them, and even libmount has native first-class mount options
for them.
> > Userspace is largely untrusted, or much lower trust anyway.
>
> Yes, which means the kernel is highly trusted. Which is why parsing complex
> binary formats, X.509 and PKCS#7, in C code in the kernel is not a great idea...
Maybe, but it's there and it's used for multiple purposes and
userspace relies on it. If you want to add a new alternative and
optional formats I don't think it would be a problem, I certainly
wouldn't mind.
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2022-12-17 2:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 3:35 [PATCH] fsverity: mark builtin signatures as deprecated Eric Biggers
2022-12-08 10:43 ` Luca Boccassi
2022-12-08 20:55 ` Eric Biggers
2022-12-08 21:37 ` Luca Boccassi
2022-12-16 20:55 ` Eric Biggers
2022-12-17 2:04 ` Luca Boccassi [this message]
2022-12-09 22:17 ` Fan Wu
2022-12-16 21:02 ` Eric Biggers
-- strict thread matches above, loose matches on Subject: below --
2022-12-08 17:41 Paul Moore
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='CAMw=ZnQNJjKVAf9xafashv8diab2Xg92M1+wNT3A37RMBVwR2Q@mail.gmail.com' \
--to=bluca@debian.org \
--cc=ebiggers@kernel.org \
--cc=jsorensen@meta.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).