All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <christoph.anton.mitterer@physik.uni-muenchen.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Bug in cryptsetup?
Date: Sun, 20 Jun 2010 00:26:15 +0200	[thread overview]
Message-ID: <1276986375.16395.22.camel@fermat.scientia.net> (raw)
In-Reply-To: <20100619221307.GA29101@tansi.org>

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

Hi Arno.

Nice to see that you've used a separate section for legacy stuff in the
FAQ :)

I guess for something like crpytsetup (with its active development and
changes to crypto theory) it's important for a FAQ that it's really
always up to date and double checked for correctness by the developers.

Therefore, may I suggest to add information to each FAQ point for/during
which version of cryptsetup it was created?
Of course this would required to check all entries again when a new
version comes out (whether they still are correct) and update the
version info.


btw: May I suggest to add the questions I put up here some weeks ago ...
about which is the "securest" algo, keysizes when using XTS,
essiv/benbi/plain when using XTS, how the masterkey is generated
using /dev/urandom (at least currently) and that one should not manually
use /dev/random as Milan said, etc.

It may also be nice to add that LRW is insecure, at least this is the
case AFAIK, and that therefore XFS was created.


Cheers,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3387 bytes --]

  reply	other threads:[~2010-06-19 22:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 17:20 [dm-crypt] Bug in cryptsetup? Si St
2010-06-19 20:16 ` Heinz Diehl
2010-06-19 21:50 ` Milan Broz
2010-06-19 22:13   ` Arno Wagner
2010-06-19 22:26     ` Christoph Anton Mitterer [this message]
2010-06-20 19:54       ` Arno Wagner
2010-06-20 12:54 Si St

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=1276986375.16395.22.camel@fermat.scientia.net \
    --to=christoph.anton.mitterer@physik.uni-muenchen.de \
    --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.