reduced block size cipher
From: Roland (rolandp66_at_yahoo.com)
Date: 04/13/04
- Next message: Paul Rubin: "Re: reduced block size cipher"
- Previous message: David Wagner: "Re: Selecting two elements minimizing Hamming distance"
- Next in thread: Paul Rubin: "Re: reduced block size cipher"
- Reply: Paul Rubin: "Re: reduced block size cipher"
- Maybe reply: Paul Rubin: "Re: reduced block size cipher"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 13 Apr 2004 13:07:47 -0700
My application needs to generate unpredictable 32-bit permutations for
a given largish key. An out-of-the-box solution is to use RC5 in
"counter mode" with a 32-bit block size. For non-technical reasons,
however, I don't have RC5 available. What I do have, however, is a
128-bit block cipher, namely AES.
Is there some generally accepted way to reduce the block size of a
trusted cipher, without compromising the security of the algorithm?
(Notwithstanding attacks based solely on the reduced block size, of
course.) Put another way, is there a way to transform AES into a
32-bit block cipher in such a way that it can be trusted at least as
far as 32-bit block RC5 of the same key length.
One scheme I have considered is to use AES as the F function in a 32
bit Feistel network. Unfortunately I am grossly under-qualified in
such matters, so I really have no idea how many rounds I need, or if
the result is secure, etc, etc.
I am aware that the AES round transformations operate on 32-bit blocks
with the exception of ShiftRow. There is an old deja/google thread
that discusses the possibility of using the remaining transformations
as a 32-bit block cipher. I feel even less qualified to do this than
the Fiestel scheme, however. What I'd prefer is a generalized scheme
that doesn't actually depend on the details of the larger block
cipher, merely its strength. Put simply, I am looking for something
at is either generally accepted, or so obviously correct that it can
withstand reasonable debate.
My application is not time constrained within reason, so something
brute force would suffice if that is the best that is available. The
app is however very space constrained, so anything requiring a swap
buffer isn't going to fly.
TIA,
Rol
- Next message: Paul Rubin: "Re: reduced block size cipher"
- Previous message: David Wagner: "Re: Selecting two elements minimizing Hamming distance"
- Next in thread: Paul Rubin: "Re: reduced block size cipher"
- Reply: Paul Rubin: "Re: reduced block size cipher"
- Maybe reply: Paul Rubin: "Re: reduced block size cipher"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|