[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2034167.Brpu2WxA6s@tauon.chronox.de>
Date: Thu, 13 Jul 2017 16:54:55 +0200
From: Stephan Müller <smueller@...onox.de>
To: herbert@...dor.apana.org.au
Cc: Eric Biggers <ebiggers3@...il.com>, linux-fscrypt@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
linux-mtd@...ts.infradead.org, linux-crypto@...r.kernel.org,
"Theodore Y . Ts'o" <tytso@....edu>,
Jaegeuk Kim <jaegeuk@...nel.org>,
Alex Cope <alexcope@...gle.com>,
Eric Biggers <ebiggers@...gle.com>
Subject: Re: [PATCH 3/6] fscrypt: use HKDF-SHA512 to derive the per-inode encryption keys
Am Mittwoch, 12. Juli 2017, 23:00:32 CEST schrieb Eric Biggers:
Hi Herbert,
This patch adds a second KDF to the kernel -- the first is found in the keys
subsystem.
The next KDF that may come in is in the TLS scope.
Would it make sense to warm up the KDF patches adding generic KDF support to
the kernel crypto API that I supplied some time ago? The advantages would be
to have one location of KDF implementations and the benefit of the testmgr.
Ciao
Stephan
Powered by blists - more mailing lists