From: "Colin Walters" <walters@verbum.org>
To: linux-fscrypt@vger.kernel.org
Subject: new libfsverity release?
Date: Sun, 17 Jan 2021 09:20:32 -0500 [thread overview]
Message-ID: <cc99418f-4171-4113-9689-afcf46695d95@www.fastmail.com> (raw)
There's been a good amount of changes since the last libfsverity release. I'm primarily interested in
https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git/commit/?id=f76d01b8ce8ce13538bac89afa8acfea9e2bdd57
I have some work in progress to update the ostree fsverity support to use it:
https://github.com/ostreedev/ostree/pull/2269
Anything blocking a release?
While I'm here, some feedback on the new library APIs:
- ostree is multi-threaded, and a process global error callback is problematic for that. I think a GLib-style "GError" type which is really just a pair of error code and string is better.
- Supporting passing the keys via file descriptor or byte array would be nice; or perhaps even better than that we should just expose the openssl types and allow passing pre-parsed key+certificate?
next reply other threads:[~2021-01-17 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 14:20 Colin Walters [this message]
2021-01-17 17:56 ` new libfsverity release? Eric Biggers
2021-01-18 18:40 ` Colin Walters
2021-01-19 18:27 ` Eric Biggers
2021-01-17 15:56 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=cc99418f-4171-4113-9689-afcf46695d95@www.fastmail.com \
--to=walters@verbum.org \
--cc=linux-fscrypt@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).