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.187])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 27 Feb 2014 22:49:56 +0100 (CET)
Date: Thu, 27 Feb 2014 22:44:53 +0100
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20140227214453.GA4618@fancy-poultry.org>
References: <530F4E30.6000204@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <530F4E30.6000204@gmail.com>
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.4
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 27.02.2014, Milan Broz wrote: 

> * Add internal "whirlpool_gcryptbug hash" for accessing flawed
>   Whirlpool hash in gcrypt (requires gcrypt 1.6.1 or above).
> 
>   The gcrypt version of Whirlpool hash algorithm was flawed in some
>   situations.

Just to be shure: if I create an encrypted partition using 
the whirlpool hash algorithm with recent cryptsetup / libgcrypt, 
does it have its full strength?