From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Truecrypt audit
Date: Sat, 17 May 2014 13:42:01 +0200 [thread overview]
Message-ID: <20140517114201.GA10381@tansi.org> (raw)
In-Reply-To: <20140517070806.GA2130@fancy-poultry.org>
On Sat, May 17, 2014 at 09:08:06 CEST, Heinz Diehl wrote:
> On 16.05.2014, Arno Wagner wrote:
>
> > I just want to warn everybody not to place too great stock
> > into these results. I have participated in similar, non-public
> > analyses and they can only ever go so deep. Cleverly hidden or
> > disguised backdoors may easily be overlooked...
>
> I agree.
>
> I posted the article because of TC's widespread use, and I'm not aware
> of any comprehensive review/audit of its source (I'm not using TC
> myself).
Posting it is fine. It does contain valuable information.
For example, I think from the report one can deduce that
TrueCrypt is not very likely to have low-value vulnerabilities,
hence, for example, ordinary law-enforcement and ordinary
criminals will likely not get in and more widely available
forensics tools will likely also not work.
I just wanted to give context which may be non-obvious to
people that have not done something like this themselves.
And yes, I am using TC, but not for secret things. "Business
Confidential" is the highest level I am willing to trust it
with.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. - Plato
next prev parent reply other threads:[~2014-05-17 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 11:11 [dm-crypt] Truecrypt audit Arno Wagner
2014-05-16 14:40 ` Chris Drake
2014-05-16 17:23 ` Arno Wagner
2014-05-17 7:08 ` Heinz Diehl
2014-05-17 11:42 ` Arno Wagner [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-16 5:02 Heinz Diehl
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=20140517114201.GA10381@tansi.org \
--to=arno@wagner.name \
--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.