From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3A45CC433E0 for ; Sun, 17 Jan 2021 14:22:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F125D2075E for ; Sun, 17 Jan 2021 14:22:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728217AbhAQOWB (ORCPT ); Sun, 17 Jan 2021 09:22:01 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:47653 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729101AbhAQOV7 (ORCPT ); Sun, 17 Jan 2021 09:21:59 -0500 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 378D75C00B2 for ; Sun, 17 Jan 2021 09:20:53 -0500 (EST) Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Sun, 17 Jan 2021 09:20:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=e+uxnTgb+hzVqdScMu8OFAWZfr4A5 bOG471Y2Tvsx0M=; b=ZqE42LiyHPvC1eImsA5/amBbqw2KDnyaKsHsQ46znB+HT n5cjCv8Sh16aR2V+FD8LocmyWAlxhYvHVWAuksor87uHE7ux8jauicqbAfUyX9dk 5YJuNzqjXmQ1r6vnAwSchBXRndWZ21u/bRM6+hOfOCJpsjVsJCmeqyECabWVY50A Rb+IeQAws3q1tBnYofa0jh6RQnFOmTFD9hVncD2xepMM6IwrwpCvDd58EsImXLlm 6xxdyOrrqfpiEKt42SYku/jcXm3XnquZvKdFCNKLOKb6hDk0yx5H0ArGc/WLNzBe fmexI5pEWA7+bjG0YzH2KFwJvQjaIGfoqgMdT3LKw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtdeigdeiiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesthdtredtre ertdenucfhrhhomhepfdevohhlihhnucghrghlthgvrhhsfdcuoeifrghlthgvrhhssehv vghrsghumhdrohhrgheqnecuggftrfgrthhtvghrnhepfedugefgvdetueevtdejgeehgf eiveefheffkeejhfevueekleettdegudegieefnecuffhomhgrihhnpehkvghrnhgvlhdr ohhrghdpghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrg hmpehmrghilhhfrhhomhepfigrlhhtvghrshesvhgvrhgsuhhmrdhorhhg X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0500920066; Sun, 17 Jan 2021 09:20:53 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-45-g4839256-fm-20210104.001-g48392560 Mime-Version: 1.0 Message-Id: Date: Sun, 17 Jan 2021 09:20:32 -0500 From: "Colin Walters" To: linux-fscrypt@vger.kernel.org Subject: new libfsverity release? Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-fscrypt@vger.kernel.org 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?