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] Few questions from a new user
Date: Fri, 10 Jan 2014 17:36:24 +0100	[thread overview]
Message-ID: <20140110163624.GA30175@tansi.org> (raw)
In-Reply-To: <CAFnMBaQDOyk=Rd-5=uuXSxnaOq46n5PB9ZzHSEZpvPXGC_vh8g@mail.gmail.com>

On Fri, Jan 10, 2014 at 16:33:56 CET, .. ink .. wrote:
> > So changing the hash does not do anything, really as the
> > attacker can only try to brute-force the passphrase and
> > that takes the same effort for SHA-1 and for SHA-512.
> >
> >
> cryptsetup 1.6.0 changed default cipher mode from cbc to xts not because
> cbc had practical issues but because xts was becoming a
> standard[1].Sometimes it makes sense to be where everybody else is if being
> anywhere is just as good as being anywhere else.If it makes not practical
> difference btw SHA1 and SHA2,then moving away from SHA1 seem like a good
> idea with the reason being having one less thing to explain in the FAQ.
> 
> [1] http://comments.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/6409

CBC has issues that XTS avoids and some of them are pretty 
practical, for example the watermark attack. SHA1 has
no such issues as it is used in LUKS.

Sorry, but changing default algorithms to reduce questions 
by people is about the worst possible reason to do it. 

Also, I do not see the questions by people as such a bad 
thing. We can point them in the right direction and maybe
learn a thing or two about what concerns LUKS users have
and maybe some of them actually read parts of the FAQ.

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
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult.  --Tony Hoare

  reply	other threads:[~2014-01-10 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 14:31 [dm-crypt] Few questions from a new user Arno Wagner
2014-01-10 15:33 ` .. ink ..
2014-01-10 16:36   ` Arno Wagner [this message]
2014-01-10 16:08 ` Milan Broz
  -- strict thread matches above, loose matches on Subject: below --
2014-01-08 22:35 Konrad
2014-01-09  6:51 ` Arno Wagner
2014-01-09 11:22   ` .. ink ..
2014-01-09 14:58     ` shmick
2014-01-10  5:04       ` Arno Wagner
2014-01-10  5:00     ` Arno Wagner

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=20140110163624.GA30175@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.