Re: The AES 256 2^119 attack



On Jul 17, 2:06 pm, Jean-Marc Desperrier <jmd...@xxxxxxxxxxxxx> wrote:
Hi,

Until now, I really couldn't understand how the AES attack could be more
effective for AES 256 than for AES 128.

There's a comment on Schneier blog that starts to offer an explanation :
        AES-192 & 256 are 'intentionally' weakened in the key expansion
        phase... The original Rijndael versions use 192-bit and 256 bit
        block sizes (a 192b key MATCHes with a 192b block & the 256b
        key MATCHes with a 256b block)

So the trouble is that AES 128's key size matches it's block size, so
there' no adaptation to do, but for AES 192 and 256 there's an
adaptation needed to use a 192/256 key with a 128 bits block size, and
that's the part that's broken ?

No what is broken is the key schedule. A stronger schedule would fix
this problem.

In reality it's not much a problem because it requires 2^61 chosen
plaintexts to be encrypted by a victim. Even if you could get
unfettered chosen texts 2^61 of them is hard to come by. And that's
even if you could at all to start with.

What this means is you can't use AES-192/256 in a hash construction
which is fine because you'd use AES-128 anyways to get a 1:1 ratio.

Tom
.



Relevant Pages

  • [PATCH] AES i586 optimized, regparm fixed
    ... The patch posted yesterday has had an issue with CONFIG_REGPARM. ... +// implements the standard AES block length ... +// AES Key Schedule Subroutine ... +// These defines generate the forward table entries ...
    (Linux-Kernel)
  • [PATCH] Drop asm i586 AES code.
    ... This patch reverts the i586 AES module. ... Redistributions in binary form must reproduce the above copyright ... -// AES Key Schedule Subroutine ... -// These defines generate the forward table entries ...
    (Linux-Kernel)
  • Re: AES Timing Attack Implementation & Karl Malbrain code...
    ... This code implements AES without using large tables. ... slow but will not be vulnerable to the DJB attack since this ... and 229 cycles per byte for the immune small table C ... Are you including or excluding the cost of setting up the key schedule? ...
    (sci.crypt)
  • [PATCH] AES i586 optimized
    ... The following patch adds an i586 optimized implementation of AES aka ... +// - Minor portability cleanups and speed optimizations ... +// An AES (Rijndael) implementation for the Pentium. ... +// AES Key Schedule Subroutine ...
    (Linux-Kernel)
  • [PATCH] AES x86-64-asm impl.
    ... +// An AES implementation for the AMD64. ... +// rsi = pointer to output ciphertext bytes ... +// AES Key Schedule Subroutine ... +// These defines generate the forward table entries ...
    (Linux-Kernel)

Quantcast