Bug#597658: possible to enable aesni-intel in squeeze?
On Wed, 2011-11-23 at 12:05 +0100, Thijs Kinkhorst wrote:
> > > the module was actually completely broken in 2.6.32 if
> > > CONFIG_CRYPTO_FIPS=y (which it is in Debian packages). However, it
> > > also looks like this was fixed in 220.127.116.11, which is incorporated in
> > > the source for the current package.
> > fyi, 2.6.32-12 & 2.6.32-29 w/ CONFIG_CRYPTO_AES_NI_INTEL=m both boot
> > successfully w/ the aesni_intel module on my Lenovo T410.
> Reading the bug log I'm tempted to conclude that this problem has been
> dealt with, at least since 18.104.22.168. The module has also since long been
> enabled in unstable.
> Would it therefore be feasible to re-enable it in an upcoming Squeeze
> point update?
While I think this is a worthwhile feature, I don't think it meets the
criteria for a stable update.
Teamwork is essential - it allows you to blame someone else.