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: Tue, 21 Jan 2020 17:16:36 -0800 From: Daniel Rosenberg <drosen@...gle.com> To: Eric Biggers <ebiggers@...nel.org> Cc: linux-fscrypt@...r.kernel.org, kernel-team@...roid.com, linux-kernel@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, Gabriel Krisman Bertazi <krisman@...labora.com>, linux-mtd@...ts.infradead.org, Richard Weinberger <richard@....at> Subject: Re: [PATCH v5 3/6] fscrypt: clarify what is meant by a per-file key On Mon, Jan 20, 2020 at 2:34 PM Eric Biggers <ebiggers@...nel.org> wrote: > > From: Eric Biggers <ebiggers@...gle.com> > > Now that there's sometimes a second type of per-file key (the dirhash > key), clarify some function names, macros, and documentation that > specifically deal with per-file *encryption* keys. > > Signed-off-by: Eric Biggers <ebiggers@...gle.com> Looks good to me. Feel free to add Reviewed-by: Daniel Rosenberg <drosen@...gle>
Powered by blists - more mailing lists