Hi, I'm sorry I didn't get around to commenting on this before it expired. I have an HP Mininote 2133, the short answer is yes and no :)
The module naming has settled down and the padlock-sha, padlock_aes and via_rng modules are at least loadable in Lucid, but aren't auto-loaded as requested in the bug report. I load them using the instructions here: http://versia.com/category/linux/#padlock dmesg shows the following output relating the those modules: [ 1.632490] padlock: Using VIA PadLock ACE for AES algorithm. [ 1.906926] padlock: Fallback driver 'sha1' could not be loaded! [ 1.906941] alg: hash: Failed to load transform for sha1-padlock: -2 [ 2.026268] padlock: Fallback driver 'sha256' could not be loaded! [ 2.026283] alg: hash: Failed to load transform for sha256-padlock: -2 [ 2.026317] padlock: Using VIA PadLock ACE for SHA1/SHA256 algorithms. [ 2.197734] VIA RNG detected I don't understand enough about the subject to know how much of a success or failure that is. Taking suggestions from https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/119295 a...@gonzo:~$ /usr/bin/openssl speed -evp aes-128-cbc -engine padlock engine "padlock" set. <snip> type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128-cbc 58657.46k 192730.14k 453469.59k 693552.61k 821348.52k The results are comparable to those in the bug #119295 comments using patched versions of openssl with the padlock engine. I guess what remains is that these modules should automatically be loaded on the hardware they support. -- Crypto engine module loading and breakage https://bugs.launchpad.net/bugs/355384 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
