The issue tracker has been moved https://gitlab.archlinux.org/archlinux/archiso/-/issues
FS#13289 - dm-crypt and aes modules
Attached to Project:
Release Engineering
Opened by Dieter Plaetinck (Dieter_be) - Sunday, 15 February 2009, 13:30 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Sunday, 22 February 2009, 19:42 GMT
Opened by Dieter Plaetinck (Dieter_be) - Sunday, 15 February 2009, 13:30 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Sunday, 22 February 2009, 19:42 GMT
|
DetailsRight now, aif does this:
dieter@dieter-ws aif [experimental] grep -R modprobe * (...) src/core/libs/lib-blockdevices-filesystems.sh:modprobe dm-crypt || show_warning modprobe 'Could not modprobe dm-crypt. no support for disk encryption' src/core/libs/lib-blockdevices-filesystems.sh:modprobe aes-i586 || show_warning modprobe 'Could not modprobe aes-i586. no support for disk encryption' We need these 2 modules to be able to use dm_crypt in aif. (note that aes-i586 also works on 64bit systems, though aes-x86-64 would be more optimized. see http://wiki.archlinux.org/index.php/System_Encryption_with_LUKS_for_dm-crypt) Can we load these modules in a cleaner way? Or should I modprobe them only when i need them (eg only when the user wants a dm_crypt volume) PS: do you also need kernel modules for dmraid? |
This task depends upon
Closed by Dieter Plaetinck (Dieter_be)
Sunday, 22 February 2009, 19:42 GMT
Reason for closing: Not a bug
Sunday, 22 February 2009, 19:42 GMT
Reason for closing: Not a bug
I'm keeping it like it is. it will even (unnecessarily?) bork out if the modules can't be loaded even though the user may not care about dm_crypt at all. Hell, anyone building images should just make sure the modules work :)