After upgrading to util-linux-2.13, I am no longer able to mount my twofish-256 encrypted file systems. Reproducible: Always Steps to Reproduce: 1. emerge --update =sys-apps/util-linux-2.13-r1 2. losetup -e twofish256 /dev/loop0 /dev/md0 (assuming that /dev/md0 is encrypted) Actual Results: losetup fails with the following error message: ioctl: LOOP_SET_STATUS: No such file or directory Expected Results: no error
*** This bug has been marked as a duplicate of bug 190819 ***
Just a question for clarification: Is this really a duplicate of bug 190819? I am talking about the cryptoloop approach and the decryption itself that is not working whereas bug 190819 is talking about the dm-crypt approach and a name mismatch of the devices. To my mind, these are two separate things.
(In reply to comment #2) > am talking about the cryptoloop approach In that case - INVALID. That patch is gone, dead, removed.
As far as I know, cryptoloop is only deprecated but not removed from util-linux. And indeed, I am able to mount file systems encrypted with 'twofish' using cryptoloop, but I am not able to use 'twofish256' as encryption algorithm.
I've the same problem! Please fix.
SAME PROBLEM, someone PLEASE FIX!
Got the same problem after upgrading to util-linux-2.13. Temporary workaround: downgrade to util-linux-2-12-r1, so you can at least access your files :)