You are not logged in.
Pages: 1
Hi,
I want to open an TrueCrypt container.
tcplay sounds the best way to do it under Arch Linux.
But it needs loop devices (like /dev/loop0) to function.
Well they are not present on my system.
The wiki article of tcplay states that:
|| Note: As of udev 181-5, the loop device module is no longer auto-loaded. ||
I guessed that I need to simply to load the kernel module named 'loop' with modprobe loop.
Well, that didn't work.
Can you guys give me a hint whats wrong here?
That seems to be easy, but I don't get it ![]()
Thanks
Offline
https://wiki.archlinux.org/index.php/Ke … e_handling
OT: I don't know your use case, but unless you're trying for some cross platform solution, I recommend against truecrypt. Consider luks instead. My 2 cents.
Last edited by graysky (2015-10-27 17:57:29)
Offline
Ok, I will look into udev.
https://wiki.archlinux.org/index.php/Ke … e_handling
OT: I don't know your use case, but unless you're trying for some cross platform solution, I recommend against truecrypt. Consider luks instead. My 2 cents.
Exactly the reason for truecrypt. We need to exchange files.
Some of us are still on windows ![]()
Offline
Truecrypt is fine, particularly if you are using tcplay to manage the containers.
Offline
The /dev/loop-control file is used to setup new loop devices. For example, losetup uses it.
If there used to be some other way involving /dev/loop0 being always present and truecrypt depends on it, try making some dummy loop0 with losetup.
If loop setup is done by you before starting truecrypt, simply use losetup and that's it.
Of course, in both cases you need to modprobe loop if it hasn't been loaded yet.
Offline
Hi,
I want to open an TrueCrypt container.
tcplay sounds the best way to do it under Arch Linux.
zuluCrypt[1] is better if you want a GUI solution to managing your TrueCrypt container in arch
Offline
Pages: 1