From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Biggers Subject: Re: [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl Date: Thu, 21 Feb 2019 10:42:03 -0800 Message-ID: <20190221184203.GB140206@gmail.com> References: <20190220065249.32099-1-ebiggers@kernel.org> <20190221054938.GA12467@sol.localdomain> <2024630.T9XyBPH5Ub@blindfold> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1gwtIT-0002S5-Dx for linux-f2fs-devel@lists.sourceforge.net; Thu, 21 Feb 2019 18:42:13 +0000 Received: from mail.kernel.org ([198.145.29.99]) by sfi-mx-4.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) id 1gwtIR-005kcP-B7 for linux-f2fs-devel@lists.sourceforge.net; Thu, 21 Feb 2019 18:42:13 +0000 Content-Disposition: inline In-Reply-To: <2024630.T9XyBPH5Ub@blindfold> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net To: Richard Weinberger Cc: linux-ext4@vger.kernel.org, "open list:ABI/API" , linux-f2fs-devel@lists.sourceforge.net, linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org, linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org, linux-fsdevel , Satya Tangirala , Paul Crowley On Thu, Feb 21, 2019 at 10:33:12AM +0100, Richard Weinberger wrote: > Eric, > > Am Donnerstag, 21. Februar 2019, 06:49:39 CET schrieb Eric Biggers: > > Hi Richard, > > > > On Thu, Feb 21, 2019 at 12:52:38AM +0100, Richard Weinberger wrote: > > > On Wed, Feb 20, 2019 at 7:55 AM Eric Biggers wrote: > > > > +#define FSCRYPT_FS_KEYRING_DESCRIPTION_SIZE \ > > > > + (CONST_STRLEN("fscrypt-") + FIELD_SIZEOF(struct super_block, s_id)) > > > > + > > > > +#define FSCRYPT_MK_DESCRIPTION_SIZE (2 * FSCRYPT_KEY_DESCRIPTOR_SIZE + 1) > > > > + > > > > +static void format_fs_keyring_description( > > > > + char description[FSCRYPT_FS_KEYRING_DESCRIPTION_SIZE], > > > > + const struct super_block *sb) > > > > +{ > > > > + sprintf(description, "fscrypt-%s", sb->s_id); > > > > +} > > > > > > I fear ->s_id is not the right thing. > > > For filesystems such as ext4 ->s_id is the name of the backing block device, > > > so it is per filesysem instance unique. > > > But this is not guaranteed. For UBIFS ->s_id is just "ubifs", always. > > > So the names will clash. > > > > > > > What name do you suggest using for UBIFS filesystems? The keyring name could be > > set by the filesystem via a fscrypt_operations callback if needed. > > IMHO the BDI name should be used. > > > Note that the keyring name isn't particularly important, since the ioctls will > > work regardless. But we might as well choose something logical, since the > > keyring name will still show up in /proc/keys. > > I'm not done with reviewing your patches, but will it be possible to use keyctl? > For the a unique name is helpful. :) > Not for adding keys, removing keys, or getting a key's status -- those are what the ioctls are for. See e.g. the discussion in patch 7 ("fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl") for why the keyrings syscalls are a poor fit for fscrypt. - Eric