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>; Sun, 20 Sep 2009 13:21:55 +0200 (CEST)
Date: Sun, 20 Sep 2009 13:28:17 +0200
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20090920112817.GA5778@fancy-poultry.org>
References: <200909182039.44953.dmcrypt-list@tpesonen.net>
	<4AB3CE76.5040502@redhat.com>
	<20090919165148.GA5619@fancy-poultry.org>
	<4AB52A50.1060503@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AB52A50.1060503@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 19.09.2009, Milan Broz wrote: 

> (I hope that udev problems will be solved soon by switching device-mapper
> to use udev directly and maintain its own, correctly written, rules.)

Today I upgraded to the latest device-mapper, and the buffer i/o errors
are completely gone.

Btw: how stable is current svn, actually? ;-)