From: Milan Broz <gmazyland@gmail.com>
To: "U.Mutlu" <for-gmane@mutluit.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] truecrypt - what's the real story behind it?
Date: Sun, 08 Feb 2015 11:03:43 +0100 [thread overview]
Message-ID: <54D7347F.1080608@gmail.com> (raw)
In-Reply-To: <mb7b8h$2m5$1@ger.gmane.org>
On 02/08/2015 10:45 AM, U.Mutlu wrote:
> Hi,
> the cryptsetup tool supports besides plain and luks, also loopaes and truecrypt.
> I now compiled truecrypt-7.1a, and it looks not bad.
Please see the https://ciphershed.org project which tries to continue with development.
> I wonder why some people say truecrypt is no more secure.
> Which part or method of truecrypt is allegedly broken? Can't be fixed?
There is no publicly known serious problem there. But there are license and other
non-technical problems. You will get more info on devel list of project above.
> And: is full truecrypt functionality integrated in cryptsetup tool? I mean the
> create-options below.
There is full support for mapping existing containers (with some exceptions,
see man page).
There is intentionally no new container creation support in cryptsetup and
I am not planning to add it.
We will better invest time to improving LUKS.
You can use tcplay or older version of truecrypt for that (or ciphershed when
released).
Milan
next prev parent reply other threads:[~2015-02-08 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 9:45 [dm-crypt] truecrypt - what's the real story behind it? U.Mutlu
2015-02-08 10:03 ` Milan Broz [this message]
2015-02-08 11:53 ` U.Mutlu
2015-02-08 12:02 ` Heinz Diehl
2015-02-08 12:09 ` Alex Elsayed
2015-02-08 12:10 ` Alex Elsayed
2015-02-09 16:16 ` Sven Eschenberg
2015-02-08 12:40 ` U.Mutlu
2015-02-09 16:12 ` Sven Eschenberg
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=54D7347F.1080608@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=for-gmane@mutluit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.