(2007/05/06) Version 1.0.5 Changes: * From this release onwards, cryptsetup-luks becomes cryptsetup. Hence, we are replacing the original main branch (with it's only 0.1 release in 2004). * Fix segfault for >32 bytes keys * Allow hashing of keys passed through stdin via --key-file=- * Remove ancient header version conversion. * No password retry for I/O errors. * Fix hang on -i 0. * Fix password retrying.
This version now supports the lrw mode as well, as mentioned in bug 183407 (there is also an ebuild...)
The new 1.0.5-ebuild is really essential. After a cryptsetup-luks, devmapper and kernel update i couldn't open my encrypted Partition even when i emerged the minor versions of the packages again. With the posted 1.0.5-ebuild my partition works fine again. The encrypted Partition has following parameters: ~#cryptsetup -v luksDump /dev/hdk1 LUKS header information for /dev/hdk1 Version: 1 Cipher name: blowfish Cipher mode: cbc-essiv:md5 Hash spec: sha1 Payload offset: 3528 MK bits: 448 MK digest: ea 46 e5 e4 df 58 2a c0 a6 54 89 28 4b 8a 7d 59 d7 6b e5 53 MK salt: 81 6e b6 ae 29 21 ac 34 5f 89 2e a1 0b 93 37 f5 db 22 f6 ab 40 e6 e1 30 85 a7 9f a3 25 f4 f4 88 MK iterations: 10 UUID: 1c8ec92e-04cc-462e-b89c-c12b6a3d6423 Key Slot 0: ENABLED Iterations: 266513 Salt: 68 7e 30 7f ac be c8 1a 3e a6 5b 1a de 60 8f 2e 38 2a 88 45 e0 83 b0 f7 f1 8a 9d e6 1f 5d f6 bc Key material offset: 8 AF stripes: 4000 Key Slot 1: DISABLED Key Slot 2: DISABLED Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED When in tried to open the partition with a older version of cryptsetup-luks i got this errors in dmesg: device-mapper: table: device /dev/hdk1 too small for target device-mapper: table: 253:1: crypt: Device lookup failed device-mapper: ioctl: error adding target to table device-mapper: ioctl: device doesn't appear to be in the dev hash table. As i said, with version 1.0.5 works everything fine and it should be put in the portage tree IMHO
I'd say the bugfix list on this is pretty critical. Suggest merge cryptsetup and cryptsetup-luks pacakges in portage.
(In reply to comment #3) > I'd say the bugfix list on this is pretty critical. Suggest merge cryptsetup > and cryptsetup-luks pacakges in portage. > why critical?
I second that: with <1.0.5 I can't mount lrw-benbi-* encrypted partitions with higher encryption level (e.g. 384 bits), so please add it to the main portage tree
$0.02 Random suggestion - especially since 1.0.5 took the liberty of changing it's naming convention (cryptsetup instead cryptsetup-luks). I haven't read through the ebuilds to see how difficult it would be, but it seems "logical" that the two apps could be converged to a single ebuild w/a 'luks' USE. Am I off my rocker?
in cvs, but make sure you emerge cryptsetup NOT cryptsetup-luks
