* Jan Glauber | 2007-03-19 15:25:39 [+0100]:
>Having fall back support for unsupported parts of an algorithm sounds like
>the right thing to me. In include/linux/crypto.h I found:
>
>/*
> * Set this bit if and only if the algorithm requires another algorithm of
> * the same type to handle corner
On Sat, 2007-03-17 at 21:28 +0100, Sebastian Siewior wrote:
> * Herbert Xu | 2007-03-17 15:12:17 [+1100]:
>
> >What exactly is the aes-special algorithm and where can I find a copy?
> The only difference between -special and -generic is the limited key
> size. It was just an example.
>
> >Yes key
* Herbert Xu | 2007-03-17 15:12:17 [+1100]:
>What exactly is the aes-special algorithm and where can I find a copy?
The only difference between -special and -generic is the limited key
size. It was just an example.
>Yes key length support is missing as far as algorithm selection
>is concerned. I
Sebastian Siewior <[EMAIL PROTECTED]> wrote:
>
> I have a little problem with the min|max keysize: /proc/crypto:
>
> name : aes
> driver : aes-special
> module : aes2
> priority : 150
> refcnt : 1
> type : cipher
> blocksize: 16
> min keysize : 24
> max
Hello,
I have a little problem with the min|max keysize: /proc/crypto:
name : aes
driver : aes-special
module : aes2
priority : 150
refcnt : 1
type : cipher
blocksize: 16
min keysize : 24
max keysize : 32
name : aes
driver : aes-generic
m
