Re: I-patch problem statement (update)

[Jari Ruusu <jari.ruusu@pp.inet.fi>]

"Janusz A. Urbanowicz" wrote:
> Jari Ruusu wrote/napisał[a]/schrieb:
> > "Janusz A. Urbanowicz" wrote:
> > > What if tomorrow some cryptographer will publish cheap, practical attack
> > > on AES? This is unlikely but possible.
> >
> > If that happens, loop-twofish is born.
> 
> And all users are forced to repatch, recompile, reboot and repent. This is
> broken. Algorithm-switch should be possible without such severe system
> modification (yes, patching kernel and rebooting may be a problem on
> RL productivity servers).

[snip]

> Oh, sure. And I have want to use, and have a license for IDEA[1]? Or
> blowfish? Or CAST? I do not ask you to include these ciphers. I only say
> that it is a very bad idea to hardcode one algorithm you personally think is
> best.

Nothing prevents you from using other cipher modules with loop-AES. Only the
AES transfer is built-in and pre-registered.
 
Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>


Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/