I've got an old hard disk, containing an encrypted partition with a file system on it. It was created (and used) several years ago, the way it was done back then was using
losetup with the
twofish encryption (via kernel module
loop_fish2) and then mounting the loop device prepared this way.
Nowadays this is not possible out of the box anymore. The kernel module is not part of the distributions, etc.
Does anybody know a way how to achieve my goal?
I found some hints in this cryptsetup manpage to use it with the options
--cipher twofish-cbc-null -s 256 -h sha512 but I get a rather surprising error message:
$ sudo cryptsetup --cipher twofish-cbc-null -s 256 -h sha512 luksOpen /dev/sdd1 dm0 Usage: cryptsetup [-?vyrq] [-?|--help] [--usage] [--version] [-v|--verbose] [--debug] [-c|--cipher=STRING] [-h|--hash=STRING] [-y|--verify-passphrase] [-d|--key-file=STRING] [--master-key-file=STRING] [--dump-master-key] [-s|--key-size=BITS] [-l|--keyfile-size=bytes] [--new-keyfile-size=bytes] [-S|--key-slot=INT] [-b|--size=SECTORS] [-o|--offset=SECTORS] [-p|--skip=SECTORS] [-r|--readonly] [-i|--iter-time=msecs] [-q|--batch-mode] [-t|--timeout=secs] [-T|--tries=INT] [--align-payload=SECTORS] [--header-backup-file=STRING] [--use-random] [--use-urandom] [--shared] [--uuid=STRING] [--allow-discards] [--header=STRING] [OPTION...] <action> <action-specific>] cryptsetup: Option --key-size is allowed only for luksFormat, create and loopaesOpen. To limit read from keyfile use --keyfile-size=(bytes).
An explanation or workaround or any other help on that would also be appreciated :-}