From: test532@codingninjas.org
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup, LUKS, plausible deniability
Date: Fri, 18 Sep 2009 00:00:50 -0400 [thread overview]
Message-ID: <200909180000.51019.test532@codingninjas.org> (raw)
In-Reply-To: <20090918012025.GB11016@tansi.org>
> I do the same. In fact I use dm-crypt with a random key
> and non-crypto randomness (mersenne-twister) for this.
>
> For full drives it works. The discussion at hand is about
> "random" areas that only cover part of a drive that is
> still in use.
Really? Where in the thread other than in your email just now does it say we
were only talking specifically about 'areas that only cover part of a drive'?
Nowhere. You may want to discontinue assuming that everyone uses dm-crypt only
like yourself.
>
> Arno
>
> On Thu, Sep 17, 2009 at 02:26:37PM -0400, test532@codingninjas.org wrote:
> > I blank out with random data any hard drive I no longer use (as it is too
> > small, too slow, Etc). These are filled with just that, random data; No
> > encrypted data left on those drives.
> >
> > =
> >
> > plausible deniability
> >
> > > On Wed, Sep 16, 2009 at 09:32:39PM +0200, Mario 'BitKoenig' Holbe wrote:
> > > > Sarah Dean <sdean12@sdean12.org> wrote:
> > > > > On Mon, 14 Sep 2009 20:04:48 -0400, test532@codingninjas.org wrote:
> > > > >>external luks header feature that Rick mentioned. dm-crypt comes
> > > > >> with practically every linux. Therefor, having dm-crypt installed
> > > > >> on one's system means nothing.
> > > >
> > > > dm-crypt on a system together with lots of random-like data just
> > > > means something more.
> > >
> > > Indeed. And the presence of encrypted/random data can be tested for
> > > with relatively low effort.
> > >
> > > Arno
> >
> > _______________________________________________
> > dm-crypt mailing list
> > dm-crypt@saout.de
> > http://www.saout.de/mailman/listinfo/dm-crypt
>
next prev parent reply other threads:[~2009-09-18 4:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 21:53 [dm-crypt] cryptsetup, LUKS, plausible deniability Ivan Stankovic
2009-09-12 22:22 ` Arno Wagner
2009-09-13 8:56 ` Tommaso
2009-09-13 9:07 ` [dm-crypt] OT: spam? Tommaso
2009-09-13 9:12 ` Rick Moritz
2009-09-13 10:00 ` Heinz Diehl
2009-09-13 18:37 ` Arno Wagner
2009-09-13 18:36 ` [dm-crypt] cryptsetup, LUKS, plausible deniability Arno Wagner
2009-09-13 19:44 ` Ivan Stankovic
2009-09-14 3:32 ` Arno Wagner
2009-09-14 7:28 ` Rick Moritz
2009-09-14 21:04 ` Arno Wagner
2009-09-13 18:04 ` Sven Eschenberg
[not found] ` <4AACA98F.2060002@redhat.com>
2009-09-13 18:28 ` Arno Wagner
2009-09-13 18:52 ` Milan Broz
2009-09-14 1:21 ` Sitaram Chamarty
2009-09-14 11:25 ` Mario 'BitKoenig' Holbe
2009-09-14 20:56 ` Arno Wagner
2009-09-14 23:45 ` Mario 'BitKoenig' Holbe
2009-09-15 0:04 ` test532
[not found] ` <6842.57094185359$1253045311@news.gmane.org>
2009-09-16 19:32 ` Mario 'BitKoenig' Holbe
2009-09-16 21:41 ` Debian User
2009-09-17 18:26 ` test532
2009-09-18 1:20 ` Arno Wagner
2009-09-18 4:00 ` test532 [this message]
[not found] ` <20090915200808.2DD0F4250006@tansi.org>
2009-09-15 20:32 ` Arno Wagner
2009-09-16 19:41 ` Mario 'BitKoenig' Holbe
2009-09-16 21:30 ` Arno Wagner
2009-09-16 1:50 ` Moji
2009-09-16 19:50 ` Mario 'BitKoenig' Holbe
2009-09-16 21:05 ` test532
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=200909180000.51019.test532@codingninjas.org \
--to=test532@codingninjas.org \
--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.