lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 17 Jan 2020 00:12:46 -0800 From: Christoph Hellwig <hch@...radead.org> To: Eric Biggers <ebiggers@...nel.org> Cc: linux-fscrypt@...r.kernel.org, linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, linux-mtd@...ts.infradead.org, Barani Muthukumaran <bmuthuku@...eaurora.org>, Gaurav Kashyap <gaurkash@...eaurora.org>, Theodore Ts'o <tytso@....edu>, Jaegeuk Kim <jaegeuk@...nel.org>, linux-api@...r.kernel.org Subject: Re: [PATCH] fscrypt: reserve flags for hardware-wrapped keys feature On Thu, Jan 16, 2020 at 11:20:08AM -0800, Eric Biggers wrote: > From: Eric Biggers <ebiggers@...gle.com> > > Reserve flags for the hardware-wrapped keys feature which is being > worked on [1]. FSCRYPT_POLICY_FLAG_HW_WRAPPED_KEY will denote that the > encryption policy needs a hardware-wrapped key to be unlocked. > FSCRYPT_ADD_KEY_FLAG_HW_WRAPPED will denote that the key being added is > a hardware-wrapped key. > > This reservation is tentative, and these codepoints may be reused if the > feature is not upstreamed. NAK. While the feature itself sounds really useful we don't just reserve format bits for code not upstream.
Powered by blists - more mailing lists