All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>
To: dm-crypt@saout.de
Subject: [dm-crypt] Latest attacks on AES-256: AES key size
Date: Sat, 01 Aug 2009 13:33:30 +0200	[thread overview]
Message-ID: <4A74280A.50403@datenparkplatz.de> (raw)

Hi,


regardless of the two requirements of related keys and the reduced
number of rounds in the latest attacks against AES-256, as Bruce
Schneier describes in his blog:

http://www.schneier.com/blog/archives/2009/07/another_new_aes.html

I have a question because Schneier points out that AES-256 uses a
"pretty lousy" key schedule.

In the second to last paragraph, he suggests that people should use
AES-128 instead, which "provides more than enough security margin for
the forseeable future".


My question is, also regarding performance issues, if this should be an
indication for users of dm-crypt, that AES-128 is a better choice than
AES-256.

Does the related-key scenario for the exploit come into play in case
there are storage arrays with multiple dm-crypt volumes?


Regards,
Ulrich

                 reply	other threads:[~2009-08-01 11:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4A74280A.50403@datenparkplatz.de \
    --to=stellplatz-nr.13a@datenparkplatz.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.