All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] yet another "lost my partition" message
Date: Fri, 15 Apr 2011 18:27:13 +0200	[thread overview]
Message-ID: <20110415162713.GC5092@tansi.org> (raw)
In-Reply-To: <4DA85469.3080503@gmail.com>

On Fri, Apr 15, 2011 at 04:21:29PM +0200, Cristian KLEIN wrote:
> On 15/04/2011 16:15, Roscoe wrote:
> > On Fri, Apr 15, 2011 at 11:52 PM, Cristian KLEIN <cristiklein@gmail.com> wrote:
> > ...
> >> A posteriori, I cannot help wonder why such pretious information isn't
> >> kept redundantly. Surely LUKS could have stored the header in 10 random
> >> sectors with an easy-to-grep "HERE I AM" banner. Wouldn't this allow
> >> users to recover the master-key (and part of the file-system) without
> >> compromising security?
> > ...
> > 
> > It's supposed to be fragile and easily destroyed, this is by design.
> 
> I think users expect it to be *secure*, i.e., if a laptop gets stolen in
> an airport, the user has no worries. I'm not sure users appreciate
> "fragile". Personally, this is not what I expect from full-disk encryption.

It is not fragile. It is designed to be fast to destroy.

It also is not "full-disk encrypton", it is partition encryption. 
The anti-forensic features require some way to destroy 
data fast and reliable. And a luksFormat will allways wipe the 
headers, no mater how you safeguard them, unless you want to store 
a backlog of old headers and anti-forensic stripes (10-20MB per 
instance) on the filesystem? With all the very serious negative 
security implicatins that has?

Cryptsetup also has adequate safeguards against accidentally
luksFormat-ing your headers and the documentation rather
strongly advises header and data backup.

The mess-up here is by Ubuntu, not cryptsetup. You are
welcome to post here of course and you are welcome to 
argue design mistakes in cryptsetup, we may have 
overlooked something after all. Currently I do not see
that.

> > Accidently running cryptsetup luksFormat is unfortunate, as is running
> > mkfs or dd on the wrong device. Good thing for backups.
> 
> Still, mkfs and dd give you a second chance (see testdisk and friends).
> Why not luksFormat?

Because it cannot without making the design a lot worse. It does
adequately warn you however. The Ubuntu people chose to hide
that warning for whatever reasons. I think I am starting to 
get angry at them....

Arno
-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 

  reply	other threads:[~2011-04-15 16:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 20:13 [dm-crypt] yet another "lost my partition" message Hugo Melo
2011-04-13  1:10 ` Arno Wagner
2011-04-13 18:06   ` Hugo Melo
2011-04-15 13:52 ` Cristian KLEIN
2011-04-15 14:15   ` Roscoe
2011-04-15 14:21     ` Cristian KLEIN
2011-04-15 16:27       ` Arno Wagner [this message]
2011-04-15 16:18     ` Arno Wagner
2011-04-15 16:13   ` Arno Wagner
2011-04-15 19:37     ` Jonas Meurer
2011-04-15 21:58       ` Arno Wagner
2011-04-16 16:37         ` Cristian KLEIN
2011-04-16 17:13           ` Rick Moritz
2011-04-15 16:58   ` [dm-crypt] Bug Report to Ubuntu regarding dangerous installer Arno Wagner
2011-04-15 19:38     ` Claudio Moretti
2011-04-15 22:01       ` Arno Wagner
2011-04-16 11:06         ` Claudio Moretti
2011-04-16 16:18           ` Cristian KLEIN
2011-04-17  0:14             ` PsiStormYamato
2011-04-17  0:20             ` M Thomas Frederiksen
2011-04-17  1:53               ` Arno Wagner
2011-04-15 20:54     ` PsiStormYamato

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=20110415162713.GC5092@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.