From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 27 Jul 2010 17:55:38 +0200 (CEST) Message-ID: <4C4F0177.3030306@redhat.com> Date: Tue, 27 Jul 2010 17:55:35 +0200 From: Milan Broz MIME-Version: 1.0 References: <20100725103458.GA26486@tansi.org> <4C4C2D3C.40306@redhat.com> <1280063664.3309.119.camel@fermat.scientia.net> <4C4C4192.60908@redhat.com> <1280097464.3309.192.camel@fermat.scientia.net> <4C4CD361.4080000@redhat.com> <1280176686.3266.106.camel@fermat.scientia.net> <4C4E9CF4.3030308@redhat.com> <1280240110.11350.11.camel@etppc09.garching.physik.uni-muenchen.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Using plain64/plain IV (initialisation vector) in dm-crypt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mario 'BitKoenig' Holbe Cc: dm-crypt@saout.de On 07/27/2010 05:45 PM, Mario 'BitKoenig' Holbe wrote: >>> Forgot about 1TB limit, it is different XTS only problem. > > I'm not intending to mention that I have any deeper understanding of the > Rogaway 2004 paper, but as far as I understand it, this limit holds at > least for all XOR-Encryption(XE)-based tweakable block ciphers. I tried to not mix that XTS/XEX 1TB problem with plain IV explanation, so it should read "1TB data limit is different problem not related to plain/plain64 IV limit" (I changed subject to mention IV only - but forgot to mention it.) Sorry for confusion:-) Milan