9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Karl Magdsick <kmagnum@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] crypto question
Date: Wed, 13 Apr 2005 18:01:36 -0400	[thread overview]
Message-ID: <cd8ecdef05041315013b6eef4@mail.gmail.com> (raw)
In-Reply-To: <20050413192328.GA13046@smp500.sitetronics.com>

 > Doesn't p9sk1 still use DES? DES was nice, but has several
> recognized ways to speed up cryptanalysis of the algorithm. 3DES
> is an alternative, but with combinations such as Rijndael-256 in
> CBC mode (or indeed, using a strong stream cipher -- Helix looks
> neat, but it's still too new, I think), I really don't see why
> we should stick with these things.

FYI, sufficiently useful quadratic approximations (XSL attack) of AES
exist to reduce all key lengths of AES to equivalent of no more than
128-bit strength.  These attacks will likely be improved in the
future.  The same class of attacks reduces Serpent to no more than
equivalent 192-bit key strength.  The key-dependent substitution
tables used in TwoFish appear to make it immune to this sort of
attack.  If you're going to pick an AES finalist block cipher, TwoFish
now appears to be the strongest of the AES finalists (especially the
legally unencumbered ciphers), despite Rijndael being chosen for AES.


-Karl


  reply	other threads:[~2005-04-13 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 22:54 Tim Newsham
2005-04-12 23:10 ` boyd, rounin
2005-04-13  0:18 ` Martin Harriss
2005-04-13  3:36   ` Tim Newsham
2005-04-13  3:44     ` boyd, rounin
2005-04-13 15:52       ` Bruce Ellis
2005-04-13 18:45         ` Tim Newsham
2005-04-13 19:23 ` Devon H. O'Dell 
2005-04-13 22:01   ` Karl Magdsick [this message]
2005-04-13 22:05     ` Devon H. O'Dell 
2005-04-13 22:16       ` Bruce Ellis

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=cd8ecdef05041315013b6eef4@mail.gmail.com \
    --to=kmagnum@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).