From: Justin Tracey <j2tracey@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Tcrypt hidden volume
Date: Tue, 02 Jul 2013 02:45:36 -0700 [thread overview]
Message-ID: <51D2A140.9050100@gmail.com> (raw)
In-Reply-To: <20130702012556.GB18826@tansi.org>
On 07/01/2013 06:25 PM, Arno Wagner wrote:
> I just saw that there is a way in TrueCrypt to protect
> the hiden volume:
> http://www.truecrypt.org/docs/hidden-volume-protection
>
> Not that this is really better, as it will leave filesystem
> annomalies and possible error messages that indicate the
> presence of a hidden volume. The TrueCrypt documentation
> claims as they make both volumes read-only immediately
> after a write that would have damaged the hidden volume,
> they preserve plausible deniability. I seriously doubt
> the validity of that. Looks more like their will
> be truncated files and metadata that indicates a
> setting to read-only. If, for example, the disk this is
> on has no CRC or other errors in its SMART log, then
> a device suddenly set read-only is not plausible.
>
> Added a warning about this as well in the man-page.
>
> Arno
Maybe this is a bit nit-picky, but as is I think the man entry goes too
into too much detail as to why and doesn't make clear enough as to what
is going to happen. IMO, it should just clearly state something to the
effect of "There is no protection of hidden volumes. If you mount a
TrueCrypt outer volume and write to it, expect data in the hidden volume
to be lost." and maybe a brief blurb about how the secrecy of hidden
volumes is questionable. The rest of the information can go into the FAQ
or somewhere.
- Justin
next prev parent reply other threads:[~2013-07-02 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 10:33 [dm-crypt] Tcrypt hidden volume Jan Janssen
2013-07-01 19:17 ` Milan Broz
2013-07-02 1:05 ` Arno Wagner
2013-07-02 1:25 ` Arno Wagner
2013-07-02 5:29 ` Milan Broz
2013-07-02 9:45 ` Justin Tracey [this message]
2013-07-02 21:54 ` Arno Wagner
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=51D2A140.9050100@gmail.com \
--to=j2tracey@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.