tags 434027 + pending
thanks
I've hit one snag implementing a fix for this. As losetup is not
available, we cannot see what precisely is loop-mounted on a certain
loop device, so we cannot loop over all loop-mounted devices and
unmount/remount them.
I've solved this by just assuming that we
On Saturday 21 July 2007 17:44, Frans Pop wrote:
The actual name of the module is loop-aes.ko. I've just verified that
if the regular loop.ko is already loaded, 'modprobe loop-aes' seems to
succeed, but does not do anything.
modprobe can be made to fail by using the --first-time option:
#
On Saturday 21 July 2007 18:07, Frans Pop wrote:
I think the current code is already smart enough that it will not try
setting up crypto support more than once.
It looks like loop is currently not modprobed separately, but pulled in
when the loop-$cipher modules are loaded. This makes it a bit
On Sunday 22 July 2007 00:33, you wrote:
It looks like loop is currently not modprobed separately, but pulled
in when the loop-$cipher modules are loaded.
Not quite correct. It is listed as a separate module in
/lib/partman/ciphers/$type/$cipher/module files, and thus loaded
separately. The
Package: partman-crypto
Severity: important
Using the daily d-i build with a businesscard image to install lenny,
My desired configuration is as follows:
/boot unencrypted
loop-aes #1 AES256, GPG key
loop-aes #2 AES256, random key
d-i tells me that it is preparing #1 but after generating
5 matches
Mail list logo
