From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id iZjLmMg3U85D for <dm-crypt@saout.de>;
 Fri, 17 Jan 2014 13:47:15 +0100 (CET)
Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com
 [IPv6:2a00:1450:4013:c00::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri, 17 Jan 2014 13:47:15 +0100 (CET)
Received: by mail-ee0-f48.google.com with SMTP id t10so2061582eei.35
 for <dm-crypt@saout.de>; Fri, 17 Jan 2014 04:47:14 -0800 (PST)
Message-ID: <52D9264F.8070905@gmail.com>
Date: Fri, 17 Jan 2014 13:47:11 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <1358734863.2409630.1389952114847.JavaMail.root@grenzecho.be>
 <52D9109B.2040906@gmail.com>
 <909167002.2417000.1389959831549.JavaMail.root@grenzecho.be>
In-Reply-To: <909167002.2417000.1389959831549.JavaMail.root@grenzecho.be>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] luks passphrase stopped working after
 cryptsetup+libgcrypt update on arch linux
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: fabrice.bongartz@grenzecho.be, dm-crypt <dm-crypt@saout.de>

On 01/17/2014 12:57 PM, Fabrice Bongartz wrote:
> Alright, thank you and sorry for posting this here. FYI A distro specific bug has been opened at https://bugs.archlinux.org/task/38550 

Seems to be this commit in gcrypt
"md: Fix Whirlpool flaw."
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commitdiff;h=0a28b2d2c9181a536fc894e24626714832619923

(It cannot be easily reversed but gcrypt build before this works.)

Unfortunately it seems that gcrypt had broken whirlpool.

TBH no idea what to do with it now...

(I wonder if other backends works, I will add some test to testsuite for this later.)

Milan