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=-6.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_PASS autolearn=unavailable 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 D4E29C4360F for ; Wed, 20 Feb 2019 18:07:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AD39820880 for ; Wed, 20 Feb 2019 18:07:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726152AbfBTSH1 convert rfc822-to-8bit (ORCPT ); Wed, 20 Feb 2019 13:07:27 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52524 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725939AbfBTSH1 (ORCPT ); Wed, 20 Feb 2019 13:07:27 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8F2D1C1217D4; Wed, 20 Feb 2019 18:07:26 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-121-129.rdu2.redhat.com [10.10.121.129]) by smtp.corp.redhat.com (Postfix) with ESMTP id 656F85D71B; Wed, 20 Feb 2019 18:07:23 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20190220065249.32099-1-ebiggers@kernel.org> References: <20190220065249.32099-1-ebiggers@kernel.org> To: Eric Biggers Cc: dhowells@redhat.com, linux-fscrypt@vger.kernel.org, Satya Tangirala , linux-api@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, keyrings@vger.kernel.org, linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, Paul Crowley Subject: Re: [RFC PATCH v3 00/18] fscrypt: key management improvements MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14022.1550686042.1@warthog.procyon.org.uk> Content-Transfer-Encoding: 8BIT Date: Wed, 20 Feb 2019 18:07:22 +0000 Message-ID: <14023.1550686042@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Wed, 20 Feb 2019 18:07:26 +0000 (UTC) Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org I have a couple of patches that add ACLs to keyrings, that you can find at the top of the branch here: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-acl I have other patches that allow tags to be used as subjects in the ACL, with a container supplying a tag, e.g.: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?h=container&id=e0fdc5613a32b9475b025f58e7a2267329b3f3a4 Might something similar be of use to you here, perhaps specifying a tag referring to the blockdev of interest rather than the container? David From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Date: Wed, 20 Feb 2019 18:07:22 +0000 Subject: Re: [RFC PATCH v3 00/18] fscrypt: key management improvements Message-Id: <14023.1550686042@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable List-Id: References: <20190220065249.32099-1-ebiggers@kernel.org> In-Reply-To: <20190220065249.32099-1-ebiggers@kernel.org> To: Eric Biggers Cc: linux-ext4@vger.kernel.org, linux-api@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, dhowells@redhat.com, linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org, linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org, linux-fsdevel@vger.kernel.org, Satya Tangirala , Paul Crowley I have a couple of patches that add ACLs to keyrings, that you can find at = the top of the branch here: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/= ?h=3Dkeys-acl I have other patches that allow tags to be used as subjects in the ACL, wit= h a container supplying a tag, e.g.: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/comm= it/?h=3Dcontainer&id=E0fdc5613a32b9475b025f58e7a2267329b3f3a4 Might something similar be of use to you here, perhaps specifying a tag referring to the blockdev of interest rather than the container? David From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [RFC PATCH v3 00/18] fscrypt: key management improvements Date: Wed, 20 Feb 2019 18:07:22 +0000 Message-ID: <14023.1550686042@warthog.procyon.org.uk> References: <20190220065249.32099-1-ebiggers@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190220065249.32099-1-ebiggers@kernel.org> Content-ID: <14022.1550686042.1@warthog.procyon.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net To: Eric Biggers Cc: linux-ext4@vger.kernel.org, linux-api@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, dhowells@redhat.com, linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org, linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org, linux-fsdevel@vger.kernel.org, Satya Tangirala , Paul Crowley List-Id: linux-api@vger.kernel.org I have a couple of patches that add ACLs to keyrings, that you can find at the top of the branch here: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-acl I have other patches that allow tags to be used as subjects in the ACL, with a container supplying a tag, e.g.: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?h=container&id=e0fdc5613a32b9475b025f58e7a2267329b3f3a4 Might something similar be of use to you here, perhaps specifying a tag referring to the blockdev of interest rather than the container? David 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=-6.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,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 596D8C10F07 for ; Wed, 20 Feb 2019 18:07:34 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3018E20880 for ; Wed, 20 Feb 2019 18:07:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="W43c/xM+" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3018E20880 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Message-ID:Date:Content-ID:MIME-Version :Subject:To:References:In-Reply-To:From:Reply-To:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=NsL/aAEMmSM9OZszz/aknZXT3tRW150TFC++4pi1xJ8=; b=W43c/xM+wlI9Ay Tz9MqXWTEiI+tQN+Q5wwUbuHazVuJOtHz7mhsCLSM9wsZk9S3nLJ2dptIoEyMxkhr97XyZxmr5KNq ZdvivoCkNjlyVgKcm5x4QFQhIDCfn/7+DX7C8ZlPb0QlcmX7teK3AHepmCy7XjDYlC3NT9lbJKjOq 9MAcOVMW3/Htz1NhBa8gUQgGemJuH63QqNulnSiTcUZfNCuPq78yAfEWE4g88u43d55BfHje3/n4B D0nXdZ7REUiuX6J0gBNbGCDUZIBe5hh97RTR0nWUpT6rF9Swp4EzEkAThC5uvrd2d0wAC/5KzV1SB cy75V642MVm5JWdknGBg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gwWHL-00082t-T3; Wed, 20 Feb 2019 18:07:31 +0000 Received: from mx1.redhat.com ([209.132.183.28]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gwWHI-00081e-N7 for linux-mtd@lists.infradead.org; Wed, 20 Feb 2019 18:07:30 +0000 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8F2D1C1217D4; Wed, 20 Feb 2019 18:07:26 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-121-129.rdu2.redhat.com [10.10.121.129]) by smtp.corp.redhat.com (Postfix) with ESMTP id 656F85D71B; Wed, 20 Feb 2019 18:07:23 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20190220065249.32099-1-ebiggers@kernel.org> References: <20190220065249.32099-1-ebiggers@kernel.org> To: Eric Biggers Subject: Re: [RFC PATCH v3 00/18] fscrypt: key management improvements MIME-Version: 1.0 Content-ID: <14022.1550686042.1@warthog.procyon.org.uk> Date: Wed, 20 Feb 2019 18:07:22 +0000 Message-ID: <14023.1550686042@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Wed, 20 Feb 2019 18:07:26 +0000 (UTC) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190220_100728_774251_D7BEACA8 X-CRM114-Status: UNSURE ( 9.41 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-mtd@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-ext4@vger.kernel.org, linux-api@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, dhowells@redhat.com, linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org, linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org, linux-fsdevel@vger.kernel.org, Satya Tangirala , Paul Crowley Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-mtd" Errors-To: linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org I have a couple of patches that add ACLs to keyrings, that you can find at the top of the branch here: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-acl I have other patches that allow tags to be used as subjects in the ACL, with a container supplying a tag, e.g.: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?h=container&id=e0fdc5613a32b9475b025f58e7a2267329b3f3a4 Might something similar be of use to you here, perhaps specifying a tag referring to the blockdev of interest rather than the container? David ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/