linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: Eric Biggers <ebiggers@kernel.org>,
	linux-fscrypt@vger.kernel.org,
	Jes Sorensen <jes.sorensen@gmail.com>
Cc: jsorensen@fb.com, kernel-team@fb.com
Subject: Re: [PATCH v2 0/3] fsverity-utils: introduce libfsverity
Date: Thu, 28 May 2020 09:22:53 -0400	[thread overview]
Message-ID: <6c829c1c-9197-122f-885c-20157b2b4c22@trained-monkey.org> (raw)
In-Reply-To: <20200527211544.GA14135@sol.localdomain>

On 5/27/20 5:15 PM, Eric Biggers wrote:
> On Mon, May 25, 2020 at 01:54:29PM -0700, Eric Biggers wrote:
>> From the 'fsverity' program, split out a library 'libfsverity'.
>> Currently it supports computing file measurements ("digests"), and
>> signing those file measurements for use with the fs-verity builtin
>> signature verification feature.
>>
>> Rewritten from patches by Jes Sorensen <jsorensen@fb.com>.
>> I made a lot of improvements; see patch 2 for details.
>>
>> This patchset can also be found at branch "libfsverity" of
>> https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git/
>>
>> Changes v1 => v2:
>>   - Fold in the Makefile fixes from Jes
>>   - Rename libfsverity_digest_size() and libfsverity_hash_name()
>>   - Improve the documentation slightly
>>   - If a memory allocation fails, print the allocation size
>>   - Use EBADMSG for invalid cert or keyfile, not EINVAL
>>   - Make libfsverity_find_hash_alg_by_name() handle NULL
>>   - Avoid introducing compiler warnings with AOSP's default cflags
>>   - Don't assume that BIO_new_file() sets errno
>>   - Other small cleanups
>>
>> Eric Biggers (3):
>>   Split up cmd_sign.c
>>   Introduce libfsverity
>>   Add some basic test programs for libfsverity
>>
> 
> Applied and pushed out to the 'master' branch.

Awesome, any idea when you'll be able to tag a new official release?

Thanks,
Jes


  reply	other threads:[~2020-05-28 13:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 20:54 [PATCH v2 0/3] fsverity-utils: introduce libfsverity Eric Biggers
2020-05-25 20:54 ` [PATCH v2 1/3] Split up cmd_sign.c Eric Biggers
2020-05-25 20:54 ` [PATCH v2 2/3] Introduce libfsverity Eric Biggers
2020-05-25 20:54 ` [PATCH v2 3/3] Add some basic test programs for libfsverity Eric Biggers
2020-05-26 22:25 ` [PATCH v2 0/3] fsverity-utils: introduce libfsverity Jes Sorensen
2020-05-26 22:43   ` Eric Biggers
2020-05-27 21:15 ` Eric Biggers
2020-05-28 13:22   ` Jes Sorensen [this message]
2020-06-05 16:44     ` Jes Sorensen
2020-06-06  0:46       ` Eric Biggers

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=6c829c1c-9197-122f-885c-20157b2b4c22@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=ebiggers@kernel.org \
    --cc=jes.sorensen@gmail.com \
    --cc=jsorensen@fb.com \
    --cc=kernel-team@fb.com \
    --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).