From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from turnserver.vnc.biz (proxy.vnc.biz [83.144.240.119]) by mail.server123.net (Postfix) with ESMTP for ; Wed, 21 Oct 2015 11:19:48 +0200 (CEST) From: Stephan Giehlow References: <053701d10b43$6c6ad4b0$45407e10$@openlimit.com> <562686B6.3060904@gmail.com> In-Reply-To: <562686B6.3060904@gmail.com> Date: Wed, 21 Oct 2015 11:19:43 +0200 (CEST) Message-ID: <005801d10be1$9fc107f0$df4317d0$@openlimit.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Language: de Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] question to crypt_format function List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Milan Broz , dm-crypt@saout.de 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? Thanks, Stephan -----Urspr=FCngliche Nachricht----- Von: Milan Broz [mailto:gmazyland@gmail.com] Gesendet: Dienstag, 20. Oktober 2015 20:24 An: Stephan Giehlow ; dm-crypt@saout.de Betreff: Re: [dm-crypt] question to crypt_format function On 10/20/2015 04:27 PM, Stephan Giehlow wrote: > we are using libcryptsetup to generate a luks container on an arm > device. The developed code comes from your example > (https://gitlab.com/cryptsetup/cryptsetup/wikis/API/crypt_luks_usage_8c-e= x ample.html). > But we have one problem: When running the code on the device, the > crypt_format function will ends with the error =93Cannot initialize > crypto backend=94. Do you have any tip to solve the error? Something is probably misconfigured on your system. If cryptsetup binary itself works, try to add debug info to your program: crypt_set_debug_level(CRYPT_DEBUG_ALL); and also try to strace it (do not use valuable password though:) If it there is still not useful explanation in log, please send the outpu= t of these logs. Thanks, Milan