From: Eric Biggers <ebiggers@kernel.org>
To: Luca Boccassi <bluca@debian.org>
Cc: fsverity@lists.linux.dev, linux-integrity@vger.kernel.org,
linux-doc@vger.kernel.org, Colin Walters <walters@verbum.org>,
Alexander Larsson <alexl@redhat.com>,
Victor Hsieh <victorhsieh@google.com>
Subject: Re: [PATCH v2] fsverity: improve documentation for builtin signature support
Date: Mon, 19 Jun 2023 22:45:13 -0700 [thread overview]
Message-ID: <20230620054513.GB1590@sol.localdomain> (raw)
In-Reply-To: <20230620031813.GA1590@sol.localdomain>
On Mon, Jun 19, 2023 at 08:18:13PM -0700, Eric Biggers wrote:
> > That list does not help, quite the opposite - libsodium seems all but
> > abandoned (last release 5 years ago, an unmaintained project is not
> > exactly what you want for your crypto primitives)
>
> libsodium has an active maintainer. Last commit was 3 months ago.
Sorry, I hadn't run 'git pull' recently. The last commit to libsodium was
actually today! I don't know why the maintainer isn't tagging new releases more
frequently. The last, 1.0.18, was 4 years ago. But it seems unfair to call an
active project "abandoned" just because of lack of tagged releases.
Anyway, this is basically a moot point now, since in v3 of this patch I dropped
the mentions of any specific crypto libraries...
- Eric
next prev parent reply other threads:[~2023-06-20 5:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 22:10 [PATCH v2] fsverity: improve documentation for builtin signature support Eric Biggers
2023-06-19 22:17 ` Eric Biggers
2023-06-19 23:04 ` Luca Boccassi
2023-06-19 23:49 ` Eric Biggers
2023-06-20 0:42 ` Luca Boccassi
2023-06-20 3:18 ` Eric Biggers
2023-06-20 5:45 ` Eric Biggers [this message]
2023-06-20 19:15 ` Luca Boccassi
2023-06-20 12:43 ` James Bottomley
2023-06-20 16:45 ` Eric Biggers
2023-06-20 19:34 ` Luca Boccassi
2023-06-20 16:55 ` Colin Walters
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=20230620054513.GB1590@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=alexl@redhat.com \
--cc=bluca@debian.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=victorhsieh@google.com \
--cc=walters@verbum.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).