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.17.13])
 (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>; Sun,  9 Mar 2014 19:32:06 +0100 (CET)
Date: Sun, 9 Mar 2014 19:32:04 +0100
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20140309183204.GA2999@fancy-poultry.org>
References: <20140309174247.GA1752@fancy-poultry.org>
 <531CAC7E.2050805@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <531CAC7E.2050805@gmail.com>
Subject: Re: [dm-crypt] SHAx and LUKS/cryptsetup
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 09.03.2014, Milan Broz wrote: 

> If you are using kernel backend (not gcrypt one)

I do :-)

> sha1 is used as test that interface works.

Ok, all good! So this is it. Thanks a lot!