From: Eric Biggers <ebiggers@kernel.org>
To: Fan Wu <wufan@linux.microsoft.com>
Cc: Victor Hsieh <victorhsieh@google.com>,
Jes Sorensen <jsorensen@meta.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, Luca Boccassi <bluca@debian.org>,
linux-integrity@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] fsverity: mark builtin signatures as deprecated
Date: Fri, 16 Dec 2022 13:02:39 -0800 [thread overview]
Message-ID: <Y5zc74DPqamqs+rH@sol.localdomain> (raw)
In-Reply-To: <20221209221719.GA3055@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Fri, Dec 09, 2022 at 02:17:19PM -0800, Fan Wu wrote:
> We have also noticed many use cases for the fs-verity build-in signatures. Proposals
> exist to use them[1]. Package managers were updated to use them[2]. We are
> successfully using them in production. Therefore we prefer to keep the existing
> build-in signatures.
>
> [1]https://fedoraproject.org/wiki/Changes/FsVerityRPM#Enable_fs-verity_in_RPM
> [2]https://github.com/rpm-software-management/rpm/issues/1121
Aren't those the same project? I already mentioned in the commit message that
it was rejected from Fedora and seems to have been abandoned. So it seems to be
something that didn't actually work out. Let me know if you know of anything to
the contrary...
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-12-16 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 3:35 [f2fs-dev] [PATCH] fsverity: mark builtin signatures as deprecated Eric Biggers
[not found] ` <eea9b4dc9314da2de39b4181a4dac59fda8b0754.camel@debian.org>
2022-12-08 20:55 ` Eric Biggers
2022-12-09 22:17 ` Fan Wu
2022-12-16 21:02 ` Eric Biggers [this message]
[not found] ` <00c7b6b0e2533b2bf007311c2ede64cb92a130db.camel@debian.org>
2022-12-16 20:55 ` Eric Biggers
2022-12-17 2:04 ` Luca Boccassi
-- 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=Y5zc74DPqamqs+rH@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=bluca@debian.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 \
--cc=wufan@linux.microsoft.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 NNTP newsgroup(s).