From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Is erasing hard disk drive mandatory?
Date: Fri, 30 May 2014 20:08:25 +0200 [thread overview]
Message-ID: <20140530180825.GA24590@tansi.org> (raw)
In-Reply-To: <CAMFqqRpk7b_1awwWOE_08JFLhtxRmzHDubz69ek96CHqRxQjCA@mail.gmail.com>
It requires psecific attack situations. For example, some application
could write data in a specific pattern that would then be visible in
the raw container. Or you could determine the size of some files or
the type of the filesystem.
Not anything usually critical, but something to keep in mind
and when being careful the crypto-wipe step is advisible.
Arno
On Fri, May 30, 2014 at 17:17:27 CEST, Stephen Cousins wrote:
> Hi Heinz,
>
> I agree. The field, by it's very nature, has varying levels of paranoia
> (rightly so as we are seeing these days) and this level is more than what I
> need for my purposes so I can save some time by not having to send random
> data to all of the drives during the build process.
>
> Steve
>
>
> On Fri, May 30, 2014 at 11:07 AM, Heinz Diehl <htd@fancy-poultry.org> wrote:
>
> > On 30.05.2014, Stephen Cousins wrote:
> >
> > > I see. So it has nothing to do with how well the data is encrypted. Just
> > > another level of protection..
> >
> > Maybe. I think the practical effects are negligible. With the first
> > minutes of use of such a disk, temporary files get written to it,
> > files get deleted, new ones get written and old stuff gets
> > overwritten. If the encryption is secure, all that doesn't really
> > matter.
> >
> > _______________________________________________
> > dm-crypt mailing list
> > dm-crypt@saout.de
> > http://www.saout.de/mailman/listinfo/dm-crypt
> >
>
>
>
> --
> ________________________________________________________________
> Steve Cousins Supercomputer Engineer/Administrator
> Advanced Computing Group University of Maine System
> 244 Neville Hall (UMS Data Center) (207) 561-3574
> Orono ME 04469 steve.cousins at maine.edu
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
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-30 18:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 13:33 [dm-crypt] Is erasing hard disk drive mandatory? Kenny Lake
2014-05-29 20:13 ` Arno Wagner
2014-05-30 13:32 ` Stephen Cousins
2014-05-30 13:42 ` Arno Wagner
2014-05-30 13:52 ` Stephen Cousins
2014-05-30 15:07 ` Heinz Diehl
2014-05-30 15:17 ` Stephen Cousins
2014-05-30 15:58 ` Thomas Bastiani
2014-05-30 17:10 ` Heinz Diehl
2014-05-30 17:24 ` Thomas Bastiani
2014-05-30 17:47 ` Heinz Diehl
2014-05-30 17:57 ` Thomas Bastiani
2014-05-30 19:03 ` Laurence Darby
2014-05-30 19:25 ` Arno Wagner
2014-05-31 8:32 ` Heinz Diehl
2014-05-30 18:08 ` Arno Wagner [this message]
2014-05-30 10:02 ` Andrew
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=20140530180825.GA24590@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.