From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] plain: opening with a wrong password
Date: Fri, 6 Feb 2015 19:20:23 +0100 [thread overview]
Message-ID: <20150206182023.GA7283@tansi.org> (raw)
In-Reply-To: <mb2hl9$h3c$1@ger.gmane.org>
On Fri, Feb 06, 2015 at 15:04:25 CET, U.Mutlu wrote:
[...]
> IMO that's a question of logic:
> A security system which stores the password in its header (ie. LUKS)
> cannot be secure against another system ("plain") that does nowhere
> store the password.
That is an argument from information-theoretical security.
In this realm, plain _does_ store the key with the encrypted
data, unless that has no structure at all. Information-theoretical
analysis is nice theoretically, but basically irrelevant for
the real world. This argument is also presented in any good
course on introduction to cryptography.
> In the case of LUKS the attacker knows more about the system
> than in the case of "plain". Ergo "plain" is more secure than LUKS.
Sorry, but wrong, see above.
> LUKS uses a static master key (as does plain). The slot passwords
> are for authenticating the access to the filesystem by the
> management tool (cryptsetup) only. Ie. the slot passwords have
> nothing to do with the encryption.
Seriously? Have you even looked at the spec or at the definition
of terms like "authentication"? Plese stop discussion things you
clearly do not understand.
Arno
--
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
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
prev parent reply other threads:[~2015-02-06 18:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 12:33 [dm-crypt] plain: opening with a wrong password U.Mutlu
2015-02-04 13:02 ` Quentin Lefebvre
2015-02-04 13:30 ` U.Mutlu
2015-02-05 11:54 ` Arno Wagner
2015-02-05 13:53 ` U.Mutlu
2015-02-05 14:04 ` U.Mutlu
2015-02-05 23:51 ` Arno Wagner
2015-02-06 14:01 ` dennis
2015-02-06 14:19 ` Michael
2015-02-06 14:47 ` U.Mutlu
2015-02-06 18:27 ` Arno Wagner
2015-02-07 17:27 ` dennis
2015-02-07 18:03 ` Heinz Diehl
2015-02-07 23:16 ` Matthias Schniedermeyer
2015-02-08 8:19 ` Heinz Diehl
2015-02-08 9:23 ` Arno Wagner
2015-02-08 9:55 ` Milan Broz
2015-02-08 10:09 ` U.Mutlu
2015-02-08 10:33 ` Milan Broz
2015-02-09 3:13 ` Arno Wagner
2015-02-08 3:07 ` Arno Wagner
2015-02-08 2:59 ` Arno Wagner
2015-02-06 14:04 ` U.Mutlu
2015-02-06 18:20 ` Arno Wagner [this message]
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=20150206182023.GA7283@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.