[arch-dev-public] [signoff] cryptsetup 1.0.5-6
Only change is in the encrypt hook: There is now an optional CRYPTO_MODULES parameter. If set, only the specified modules are added, instead of all crypto modules: Example (which works for me): CRYPTO_MODULES="aes-x86_64 sha256-generic"
Only change is in the encrypt hook: There is now an optional CRYPTO_MODULES parameter. If set, only the specified modules are added, instead of all crypto modules:
Example (which works for me): CRYPTO_MODULES="aes-x86_64 sha256-generic" anyone? is this movable to core?
Am Sonntag, 2. März 2008 schrieb Thomas Bächler: thanks greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Wed, Mar 12, 2008 at 2:05 PM, Tobias Powalowski <t.powa@gmx.de> wrote:
Am Sonntag, 2. März 2008 schrieb Thomas Bächler:
Only change is in the encrypt hook: There is now an optional CRYPTO_MODULES parameter. If set, only the specified modules are added, instead of all crypto modules:
Example (which works for me): CRYPTO_MODULES="aes-x86_64 sha256-generic" anyone? is this movable to core?
I'll signoff and say "go ahead", I think Thomas depends on this himself, so if it's broken, he wouldn't have released it 8)
Aaron Griffin schrieb:
I'll signoff and say "go ahead", I think Thomas depends on this himself, so if it's broken, he wouldn't have released it 8)
I do, and I'll signoff myself :)
participants (3)
-
Aaron Griffin
-
Thomas Bächler
-
Tobias Powalowski