From mboxrd@z Thu Jan 1 00:00:00 1970 From: Herbert Xu Subject: Re: dm-crypt IV generation (summary) Date: Thu, 6 Apr 2017 17:29:57 +0800 Message-ID: <20170406092957.GA31341@gondor.apana.org.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Binoy Jayan , Mike Snitzer , Gilad Ben-Yossef , dm-devel@redhat.com, Mikulas Patocka , linux-crypto@vger.kernel.org, Milan Broz , Alasdair Kergon To: Ondrej Mosnacek Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com List-Id: linux-crypto.vger.kernel.org On Fri, Mar 10, 2017 at 02:44:26PM +0100, Ondrej Mosnacek wrote: > Hi all, > > I was tasked to post a summary the whole dm-crypt IV generation > problem and all the suggested solutions along with their drawbacks, so > here it goes... Thanks for the summary. It looks good to me. Something else to keep mind is the potential to reuse IV generators. Recently a patch has been proposed for fscrypt that also makes use of essiv (search for "fscrypt: Add support for AES-128-CBC"). It would be great if we could reuse the same code for both dm-crypt and fscrypt. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt