dimanche 14 avril 2013

CONFIG_DM_CRYPT: is not set (required for cryptsetup)

Problème

* Messages for package sys-fs/cryptsetup-1.4.3:

*   CONFIG_DM_CRYPT:   is not set (required for cryptsetup)
*
* Please check to make sure these options are set correctly.
* Failure to do so may cause unexpected problems.
* This ebuild introduces a new set of scripts and configuration
* than the last version. If you are currently using /etc/conf.d/cryptfs
* then you *MUST* copy your old file to:
* /etc/conf.d/dmcrypt
* Or your encrypted partitions will *NOT* work.
* Please see the example for configuring a LUKS mountpoint
* in /etc/conf.d/dmcrypt
*
* If you are using baselayout-2 then please do:
* rc-update add dmcrypt boot
* This version introduces a command line arguement 'key_timeout'.
* If you want the search for the removable key device to timeout
* after 10 seconds add the following to your bootloader config:
* key_timeout=10
* A timeout of 0 will mean it will wait indefinitely.
*
* Users using cryptsetup-1.0.x (dm-crypt plain) volumes must use
* a compatibility mode when using cryptsetup-1.1.x. This can be
* done by specifying the cipher (-c), key size (-s) and hash (-h).
* For more info, see http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup




Solution


- Mettre à jour le kernel
- Dans la config du kernel : device drivers -> Multiple devices driver support (RAID and LVM) -> Crypt target support 
- emerge sys-fs/cryptsetup

Liens :

PoweredByGento