Hi,
Simon Mackinlay wrote (31 Aug 2011 09:47:10 GMT) :
> So perhaps the right thing to do is to provide a _very_ early hook
> to modprobe arch-specific crypto modules (at least, until the crypto
> folk implement some kind of runtime patching) ?
Is it sufficient to add aesni-intel to /etc/initramf
Rebuilding the kernel with CRYPTO_AES_NI_INTEL=y (and for that matter
CRYPTO_PCRYPT=y) produces the expected result (ie, hw-encryption) - even in
the...
FS (say, ext4) stacked on LV stacked on VG stacked on PV stacked on dm-crypt
blockdev stacked on partition
... case (which, now that I have a
Actually this may be more serious than it first seems.
A typical* user might have...
FS (say, ext4) stacked on LV stacked on VG stacked on PV stacked on dm-crypt
blockdev stacked on partition (a reasonably common/ recommended deployment,
TRIM issues notwithstanding).
In this case - the arch-s
Package: cryptsetup
Version: 2:1.3.0-3
Severity: normal
It seems as if arch-specific crypto modules (for example - aesni-intel) are
loaded _after_ the root and swap devices are luksOpen'd (other devices are
open'd later in boot, late enough that the forced modprobe (I have aesni-intel
in /etc/mod
4 matches
Mail list logo
