From: Matthias Schniedermeyer <ms@citd.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Re2: nuke password to delete luks header
Date: Wed, 15 Jan 2014 13:59:29 +0100 [thread overview]
Message-ID: <20140115125929.GA12852@citd.de> (raw)
In-Reply-To: <20140115124024.GA1918@tansi.org>
On 15.01.2014 13:40, Arno Wagner wrote:
> On Wed, Jan 15, 2014 at 12:39:44 CET, Matthias Schniedermeyer wrote:
> > Or for the Truecypt example:
> > Try to prove that you don't have a hidden volume. It's a documented
> > feature of Truecypt, so a LEO just assumes that you use it, regardless
> > of you actually using one or not.
>
> My advice here is to have a hidden volume and to immediately admit
> it and open it for them. You can even explain that having one with
> harmless data is the only way to prove you do not have one with
> illicit data in it.
I don't think that proves anything.
At least in theory it should be possible to have several hidden volumes.
Or have stacked hidden volumes.
(Due to lack of knowledge i don't actually know if Truecrypt (by itself)
actually supports such a thing.)
--
Matthias
next prev parent reply other threads:[~2014-01-15 12:59 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 2:10 [dm-crypt] nuke password to delete luks header Jim O'Gorman
2014-01-14 2:41 ` .. ink ..
2014-01-14 2:52 ` Jim O'Gorman
2014-01-14 4:04 ` .. ink ..
2014-01-14 4:36 ` Arno Wagner
2014-01-14 5:00 ` .. ink ..
2014-01-14 7:11 ` Arno Wagner
2014-01-14 12:05 ` .. ink ..
2014-01-14 14:34 ` Arno Wagner
2014-01-14 19:22 ` .. ink ..
2014-01-15 19:36 ` Milan Broz
2014-01-16 11:50 ` Arno Wagner
2014-01-14 4:30 ` Arno Wagner
2014-01-14 5:01 ` Jim O'Gorman
2014-01-14 7:39 ` [dm-crypt] Re2: " Arno Wagner
2014-01-14 22:42 ` Jonas Meurer
2014-01-15 6:01 ` Arno Wagner
2014-01-15 10:00 ` Jonas Meurer
2014-01-15 10:47 ` Arno Wagner
2014-01-15 11:39 ` Matthias Schniedermeyer
2014-01-15 12:40 ` Arno Wagner
2014-01-15 12:59 ` Matthias Schniedermeyer [this message]
2014-01-15 13:38 ` .. ink ..
2014-01-15 20:27 ` [dm-crypt] " Milan Broz
2014-01-16 9:50 ` Ondrej Kozina
2014-01-16 10:30 ` Thomas Bastiani
2014-01-16 13:09 ` Florian Junghanns
2014-01-16 19:33 ` Milan Broz
2014-01-16 20:09 ` helices
2014-01-16 20:11 ` Iggy
2014-01-16 21:36 ` Matthias Schniedermeyer
2014-01-16 21:55 ` Arno Wagner
2014-01-16 22:49 ` Claudio Moretti
2014-01-17 8:17 ` Thomas Bastiani
2014-01-17 23:18 ` Claudio Moretti
2014-01-18 8:43 ` Arno Wagner
2014-01-18 12:42 ` Claudio Moretti
2014-01-18 19:18 ` Arno Wagner
2014-01-16 20:18 ` Matthias Schniedermeyer
2014-01-16 20:28 ` .. ink ..
2014-01-16 21:02 ` Brian
2014-01-16 21:24 ` Arno Wagner
2014-01-16 20:59 ` Milan Broz
2014-01-16 21:43 ` Arno Wagner
2014-01-17 12:43 ` Jonas Meurer
2014-01-17 13:12 ` Arno Wagner
2014-01-17 14:27 ` Jonas Meurer
2014-01-17 15:16 ` Matthias Schniedermeyer
2014-01-17 14:32 ` Rick Moritz
2014-01-17 14:32 ` Jonas Meurer
2014-01-17 14:57 ` Arno Wagner
2014-01-17 14:51 ` Heiko Rosemann
2014-01-17 15:10 ` Arno Wagner
2014-01-16 12:01 ` Arno Wagner
2014-01-16 11:59 ` Arno Wagner
2014-01-21 22:40 ` Jonas
2014-01-23 21:26 ` Milan Broz
2014-01-23 22:11 ` .. ink ..
2014-01-23 22:30 ` Milan Broz
2014-01-23 23:43 ` Arno Wagner
2014-01-27 9:04 ` Jonas Meurer
2014-01-27 12:44 ` Arno Wagner
2014-01-27 20:30 ` Milan Broz
2014-01-28 10:28 ` Jonas Meurer
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=20140115125929.GA12852@citd.de \
--to=ms@citd.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox