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] Basics
Date: Sun, 27 Sep 2015 16:34:28 +0200	[thread overview]
Message-ID: <20150927143427.GA13607@tansi.org> (raw)
In-Reply-To: <20150927141533.GP14230@yeono.kjorling.se>

On Sun, Sep 27, 2015 at 16:15:34 CEST, Michael Kjörling wrote:
> On 27 Sep 2015 16:08 +0200, from arno@wagner.name (Arno Wagner):
> >> Whether is 'cleft cam synod lacy yr wok' more secure than 'nXRUzbL6' (a 
> >> random 'pwgen' generated password)?
> > 
> > Also refer to FAQ Item 5.1. The first pasphrase will have something
> > like 13...29 bits of entropy,
> 
> Now I'm curious. Given that 6 × log2(6^5) ~ 77.6, and Diceware uses a
> 6^5 word dictionary, how did you arrive at the range 13 through 29
> bits of entropy?
> 
> Note that even when using the English Diceware word list, you cannot
> assume the same entropy per character or word as in English prose
> precisely because the advice for generating Diceware passphrases
> specifically suggest _repeating the process_ if one ends up with a
> passphrase that actually makes sense.

I have no idea what Diceware does, and there was no reference to
this being a Diceware-generated passphrase. If it is, the 
calculation is different.

Ok, judging from their website: 8000 words gives them 13 bit 
per word. Ok, with that they are at 77 bits for said passphrase,
which is much better and likely secure.

The difference to ordinary words is most likely due to them 
having chosen words far shorter than is average in english. 

Regards,
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

  reply	other threads:[~2015-09-27 14:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 17:33 [dm-crypt] Basics Mike Nagie
2015-09-25 17:55 ` Mistave
2015-09-25 19:44 ` Michael Kjörling
2015-09-25 19:48   ` Michael Kjörling
2015-09-25 21:48   ` Mike Nagie
2015-09-25 22:24     ` Michael Kjörling
2015-09-25 23:03       ` Arno Wagner
2015-09-26  7:14       ` Mike Nagie
2015-09-26  7:32         ` Mistave
2015-09-26  8:27           ` Mike Nagie
2015-09-26 10:24             ` Mistave
2015-09-26 13:12         ` Robert Nichols
2015-09-26 15:38         ` Michael Kjörling
2015-09-27 11:08           ` Mike Nagie
2015-09-27 13:47             ` Michael Kjörling
2015-09-27 14:08             ` Arno Wagner
2015-09-27 14:15               ` Michael Kjörling
2015-09-27 14:34                 ` Arno Wagner [this message]
2015-09-27 16:12                 ` Mike Nagie
2015-09-27 16:51                   ` Michael Kjörling
2015-09-27 18:20                     ` Mike Nagie
2015-09-27 18:55                   ` Heinz Diehl
2015-09-27 18:57                     ` Heinz Diehl
2015-09-27 21:50                     ` Mike Nagie
2015-09-27 22:08                       ` Michael Kjörling
2015-09-28 20:11                       ` Heinz Diehl
2015-09-29 10:52                         ` Mike Nagie
2015-09-30 12:16                         ` Mike Nagie
2015-09-30 15:00                           ` Arno Wagner
2015-09-30 17:49                             ` Mike Nagie
2015-09-30 19:27                               ` Arno Wagner
2015-09-30 15:40                           ` Heinz Diehl
2015-09-25 20:12 ` 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=20150927143427.GA13607@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.