From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: Jes Sorensen <jsorensen@fb.com>,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [ANNOUNCE] fsverity-utils v1.1
Date: Sun, 14 Jun 2020 23:51:25 -0700 [thread overview]
Message-ID: <20200615065125.GB3100@sol.localdomain> (raw)
I've released fsverity-utils v1.1:
Git: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git/tag/?h=v1.1
Tarball: https://kernel.org/pub/linux/kernel/people/ebiggers/fsverity-utils/v1.1/
Release notes:
* Split the file measurement computation and signing functionality
of the `fsverity` program into a library `libfsverity`. See
`README.md` and `Makefile` for more details.
* Improved the Makefile.
* Added some tests. They can be run using `make check`. Also added
`scripts/run-tests.sh` which does more extensive prerelease tests.
* Lots of cleanups and other small improvements.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
reply other threads:[~2020-06-15 6:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200615065125.GB3100@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jsorensen@fb.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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).