From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 1IQjR9uN7fae for ; Sun, 30 Dec 2012 00:39:14 +0100 (CET) Received: from mail-ea0-f177.google.com (mail-ea0-f177.google.com [209.85.215.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sun, 30 Dec 2012 00:39:13 +0100 (CET) Received: by mail-ea0-f177.google.com with SMTP id c10so4647694eaa.36 for ; Sat, 29 Dec 2012 15:39:13 -0800 (PST) Message-ID: <50DF7F1F.1020007@gmail.com> Date: Sun, 30 Dec 2012 00:39:11 +0100 From: Milan Broz MIME-Version: 1.0 References: <50DF72CE.3060801@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] (no subject) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ".. ink .." Cc: dm-crypt@saout.de On 12/30/2012 12:15 AM, .. ink .. wrote: > > i meant "tcrypt" for "truecrypt". > > Way to test. > 1. create a truecrypt mapper. > 2. call "crypt_init_by_name" to create context through the opened mapper and the function call will fail. interesting, cryptsetup close (action_close) uses this and it doesn't fail here... How do you create that truecrypt device? (It cannot use devices directly mapped by truecrypt itself, cryptsetup will handle only devices which have proper DM UUID, activated by cryptsetup). Can you send me some code sample which fails? Milan