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 ReOKriFDTyIX for ; Wed, 11 Sep 2013 08:05:28 +0200 (CEST) Received: from mail-ee0-x22a.google.com (mail-ee0-x22a.google.com [IPv6:2a00:1450:4013:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Wed, 11 Sep 2013 08:05:28 +0200 (CEST) Received: by mail-ee0-f42.google.com with SMTP id b45so4363984eek.15 for ; Tue, 10 Sep 2013 23:05:22 -0700 (PDT) Message-ID: <5230081C.4080205@gmail.com> Date: Wed, 11 Sep 2013 08:05:16 +0200 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Truecrypt and cryptdisks_start: failing with CRYPTTAB_OPTION_tcrypt-system: bad variable name List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Claudio Moretti Cc: dm-crypt@saout.de On 11.9.2013 2:00, Claudio Moretti wrote: > Hello everyone, > > I have recently (aka today) encrypted my Windows system partition > with Truecrypt. My system is booting fine (both Windows and Debian > sid), but I have the necessity of mounting the Windows partition when > booting Debian (all my files are there). > > I found out that with a simple entry in /etc/crypttab this should be > easily done, but when I tried it, I got the following error: > > [....] Starting crypto disk.../usr/sbin/cryptdisks_start: 1: export: > CRYPTTAB_OPTION_tcrypt-system: bad variable name > > > I thought it was a bad-something happening with the Debian version of > cryptsetup (2:1.6.1-1), so I downloaded and compiled the 1.7.0-git > version and tried to use it. The same error occurs No, the cryptsetup binary version is fine. If you have system disk encryption, you need 1.6.2 with fixes but otherwise the support is in 1.6.1 already. What is missing is Debian init scripts/systemd/cryptsetup scripts support for new crypttab keyword. Parsing of crypttab is not part of upstream cryptsetup so this report should go into Debian bugzilla. But if you are able to use systemd 206 as service manager, it should work by default... Milan