From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com
 [IPv6:2a00:1450:400c:c05::22d])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed, 21 Oct 2015 11:46:41 +0200 (CEST)
Received: by wicfx6 with SMTP id fx6so82770490wic.1
 for <dm-crypt@saout.de>; Wed, 21 Oct 2015 02:46:40 -0700 (PDT)
References: <053701d10b43$6c6ad4b0$45407e10$@openlimit.com>
 <562686B6.3060904@gmail.com> <005801d10be1$9fc107f0$df4317d0$@openlimit.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <56275EFE.4030301@gmail.com>
Date: Wed, 21 Oct 2015 11:46:38 +0200
MIME-Version: 1.0
In-Reply-To: <005801d10be1$9fc107f0$df4317d0$@openlimit.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] question to crypt_format function
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: Stephan Giehlow <stephan.giehlow@openlimit.com>, dm-crypt@saout.de

On 10/21/2015 11:19 AM, Stephan Giehlow wrote:
> Hi,
> 
> thanks for the fast answer. The cryptsetup binary itself works on the arm
> device. I added debug logging to my source. When I perform the
> crypt_format function I can see the Log "#Crypto backend () initialized".
> On my developer virtual machine are more information - like "#Crypto
> backen (Linux 3.7.10-1.32-desktop kernel CryptoAPI) initialized".
> 
> Is there any missing additional call to initialize any crypto backend?

No, it should be automatic. (The example works as it is in sources.)
So it depends what crypto backend libcryptsetup was compiled for (empty string
in message is definitely wrong), you apparently
use non-standard configuration (kernel crypto API is not default backend).

Anyway, I cannot say more without reading logs and strace.

Milan