From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Tue, 27 Jul 2010 10:46:50 +0200 (CEST)
Message-ID: <4C4E9CF4.3030308@redhat.com>
Date: Tue, 27 Jul 2010 10:46:44 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <AANLkTilnJU3L9ejwDVNTPGt14IAA3MqCRXZjFRY6uNpv@mail.gmail.com>	<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>
In-Reply-To: <1280176686.3266.106.camel@fermat.scientia.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Using plain64/plain IV (initialisation vector) in
 dm-crypt
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Christoph Anton Mitterer <christoph.anton.mitterer@physik.uni-muenchen.de>
Cc: dm-crypt@saout.de

This thread is going crazy... :)

1) Facts about using plain IV generator:

- "plain" IV is 32bit only, supported by all kernels
- you should avoid using it for >2TB devices
- it will remain this way because of backward compatibility (howgh:-)

- "plain64" is fully 64bit, available since kernel 2.6.33
- for device < 2TB it produces the same output as "plain"

=> use plain64 for new devices if you want to use tweakable encryption
mode like XTS (or LRW), e.g. cryptsetup -c aes-xts-plain64

p.s.
Never use plain* IV for CBC mode, use ESSIV there.
<joke>If you are using ECB mode, you are lost anyway.</joke>

2) crypsetup should have always safe defaults.
It is aes-cbc-essiv:sha256 with 256bit key currently.


3) For the resize - we cannot catch all situations, someone can
dd LUKS disk to another bigger volume without "resize" command.

Tools will suggest using plain64 but it cannot force it.


> So you guess the the 1TB limit could be actually ...

Forgot about 1TB limit, it is different XTS only problem.
We mixed up two unrelated problems here.

Milan