From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd@fancy-poultry.org>
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.171]) by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Sat, 19 Sep 2009 18:45:29 +0200 (CEST)
Date: Sat, 19 Sep 2009 18:51:48 +0200
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20090919165148.GA5619@fancy-poultry.org>
References: <200909182039.44953.dmcrypt-list@tpesonen.net>
	<4AB3CE76.5040502@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AB3CE76.5040502@redhat.com>
Subject: Re: [dm-crypt] Question on LUKS master key digest and its effect on
 security
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: dm-crypt@saout.de

On 18.09.2009, Milan Broz wrote: 

> Yes it was hardcoded to use sha1. But it is no longer true anyway.
> Using another hash (all algorithms provided by libgcrypt) is already
> implemented in devel code.

As reported some weeks ago, the buffer i/o errors are still present with
the latest svn code (from today):

[....]
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 32
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 4
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 5
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 6
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 7
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 8
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 9
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 10
Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 11
Sep 19 18:35:57 liesel kernel: __ratelimit: 37 callbacks suppressed
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 64
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 65
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 64
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 65
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 120
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 121
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 120
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 121
Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 8
[....]

cryptsetup-1.0.7 works fine.