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] [ANNOUNCE] cryptsetup 1.6.4
Date: Sat, 1 Mar 2014 20:44:24 +0100	[thread overview]
Message-ID: <20140301194424.GA3927@tansi.org> (raw)
In-Reply-To: <20140301165025.GA1719@fancy-poultry.org>

On Sat, Mar 01, 2014 at 17:50:25 CET, Heinz Diehl wrote:
> On 01.03.2014, Milan Broz wrote: 
> 
> > (I would say - this is a good lesson to think why there are safe defaults
> > and why you should not change encryption parameters without good reason :-)
> 
> It's not always the facts which leads to action, but the peoples
> assumptions and beliefs. After all, there's a general disbelief in all
> things the NSA put their fingers on. That said, it is not hard for me
> to understand what people moves to use whirlpool over SHAx..

Which leads to its own set of problems, as recently seen...

The advice is not to change crypto parameters unless you
really know what you are doing. Most people do not and make
matters worse. The only thing we can try to do heres is to 
explain, as, e.g., FAQ Item 5.20 "LUKS is broken! It uses SHA-1!"
tries to do. Just changing some things with no clear understanding 
why they may or may not be bad is worse than running with the 
defaults. 

Face it, unless you are an experty for the use of crypto,
you have no chance of coocking up your own parameter set
that is reliably "better", but have a good chance of making 
things worse.

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

  reply	other threads:[~2014-03-01 19:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 14:39 [dm-crypt] [ANNOUNCE] cryptsetup 1.6.4 Milan Broz
2014-02-27 17:30 ` Thomas Bächler
2014-02-28  7:51   ` Milan Broz
2014-02-28 11:29   ` Milan Broz
2014-02-28 11:38     ` Arno Wagner
2014-02-28 21:26     ` Sven Eschenberg
2014-02-28 21:46       ` Arno Wagner
2014-02-28 22:06         ` Sven Eschenberg
2014-02-28 23:27           ` Arno Wagner
2014-03-01  7:39             ` Sven Eschenberg
2014-03-01  8:35               ` Milan Broz
2014-03-01 11:32                 ` Sven Eschenberg
2014-03-01 16:50                 ` Heinz Diehl
2014-03-01 19:44                   ` Arno Wagner [this message]
2014-03-02  7:35                     ` Heinz Diehl
2014-03-02 15:17                       ` Arno Wagner
2014-03-01 13:50               ` Arno Wagner
2014-02-27 21:44 ` Heinz Diehl
2014-02-27 22:36   ` 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=20140301194424.GA3927@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.