From: Milan Broz <gmazyland@gmail.com>
To: Claudio Moretti <flyingstar16@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Truecrypt and cryptdisks_start: failing with CRYPTTAB_OPTION_tcrypt-system: bad variable name
Date: Wed, 11 Sep 2013 08:05:16 +0200 [thread overview]
Message-ID: <5230081C.4080205@gmail.com> (raw)
In-Reply-To: <CAMw1ynR_6dYYqry1zUkAqSBXxfOGHFm2Zqtuqfm7A8+jQRC7Gw@mail.gmail.com>
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
prev parent reply other threads:[~2013-09-11 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 0:00 [dm-crypt] Truecrypt and cryptdisks_start: failing with CRYPTTAB_OPTION_tcrypt-system: bad variable name Claudio Moretti
2013-09-11 0:16 ` .. ink ..
2013-09-11 12:33 ` Claudio Moretti
2013-09-11 13:09 ` Claudio Moretti
2013-09-11 13:10 ` .. ink ..
2013-09-11 15:02 ` Claudio Moretti
2013-09-11 20:10 ` .. ink ..
2013-09-11 0:42 ` Arno Wagner
2013-09-11 6:05 ` Milan Broz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5230081C.4080205@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=flyingstar16@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox