From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: Colin Walters <walters@verbum.org>,
Luca Boccassi <luca.boccassi@microsoft.com>,
Jes Sorensen <jsorensen@fb.com>
Subject: [ANNOUNCE] fsverity-utils v1.3
Date: Tue, 19 Jan 2021 14:55:33 -0800 [thread overview]
Message-ID: <YAdjZRKzblp5ypJ3@sol.localdomain> (raw)
I've released fsverity-utils v1.3:
Git: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git/tag/?h=v1.3
Tarball: https://kernel.org/pub/linux/kernel/people/ebiggers/fsverity-utils/v1.3/
Release notes (these can also be found in the NEWS.md file):
* Added a `fsverity digest` subcommand.
* Added `libfsverity_enable()` and `libfsverity_enable_with_sig()`.
* Added basic support for Windows builds of `fsverity` using MinGW.
* `fsverity` now defaults to 4096-byte blocks on all platforms.
* libfsverity now will use SHA-256 with 4096-byte blocks if the
`hash_algorithm` and `block_size` fields are left 0.
* `make install` now installs a pkg-config file for libfsverity.
* The Makefile now uses pkg-config to get the libcrypto build flags.
* Fixed `make check` with `USE_SHARED_LIB=1`.
- Eric
reply other threads:[~2021-01-19 22:57 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=YAdjZRKzblp5ypJ3@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jsorensen@fb.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=luca.boccassi@microsoft.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).