DM-Crypt Archive on 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:18:29 +0200	[thread overview]
Message-ID: <20110415161829.GB5092@tansi.org> (raw)
In-Reply-To: <BANLkTinno4SB8H_TS7qPeSfQDEhehSGA_Q@mail.gmail.com>

On Sat, Apr 16, 2011 at 12:15:59AM +1000, 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 don't think we should bother with complicated safeguards for people
> doing silly things. That installer interface should be modified long,
> long, long before the on-disk format is.

Indeed. Sorry, but security is always a trade-off against
usability. The trade-off in LUKS is still sound.
 
> Accidently running cryptsetup luksFormat is unfortunate, as is running
> mkfs or dd on the wrong device. Good thing for backups.

It is rather unlikely to accidentally do this with cryptsetup
in interactive mode. It warns you and asks for an uppercase "YES".
This seems to be a serious bug n the Ubuntu installer, which
seems to use --batch-mode on cryptsetup and then do inadequate
(one may say "incompetent") checking and asking. It also
seems not to warn clear enough that this will kill the
existing LUKS partition instead of mounting it. Pretty
bad design. Doing bad things to your partitions and filesystems
should be hard not easy. Don't forget that if you do this
to a FAT filesystem you also lose all data. It is not that 
LUKS is special in that regard.

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 

  parent reply	other threads:[~2011-04-15 16:18 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
2011-04-15 16:18     ` Arno Wagner [this message]
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=20110415161829.GB5092@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox