From: Alex Elsayed <eternaleye@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] truecrypt - what's the real story behind it?
Date: Sun, 08 Feb 2015 04:10:30 -0800 [thread overview]
Message-ID: <mb7jnn$qi6$2@ger.gmane.org> (raw)
In-Reply-To: mb7jl0$qi6$1@ger.gmane.org
Alex Elsayed wrote:
> Heinz Diehl wrote:
>
>> On 08.02.2015, U.Mutlu wrote:
>>
>>> Then I wonder if the NSA/CIA/DHS etc. was involved in the decision of
>>> the authors to abondon truecrypt developement, or was there maybe a mole
>>> among
>>> the devs?... conspiracy mode off :-)
>>
>> Nobody knows but the Truecrypt devs. IMHO the reasons to abandon TC
>> development was rather financial ones.
>>
>>> The advantage of truecrypt, as I see it, is that it is a multiplatform
>>> solution; works even under the Windows cr*p
>>
>> If you use Wind*ws as your platform, you'll most likely have a lot more
>> serious security problems than a simple "how reliable is TC"... ;-)
>
> Also, while IIRC it doesn't support encrypted rootfs, there _is_ FreeOTFE
> for opening LUKS volumes on Windows.
Correction; it seems FreeOTFE died while I wasn't looking. This seems to be
the replacement: https://en.wikipedia.org/wiki/DoxBox
next prev parent reply other threads:[~2015-02-08 12:15 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
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 [this message]
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='mb7jnn$qi6$2@ger.gmane.org' \
--to=eternaleye@gmail.com \
--cc=dm-crypt@saout.de \
/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.