News for hackers. Stuff that matters.
Re:Truecrypt report by Quiark on Thursday April 02, 2015 @11:21AM (#9311201)
The benefit of TrueCrypt over LUKS is that it's portable to Windows and Mac.
Re:Truecrypt report by nbaksalyar on Thursday April 02, 2015 @11:25AM (#9311226)
And it seems that LUKS supports full disk encryption only, while TrueCrypt allows to use encrypted containers (i.e. single files).
Re:Truecrypt report by ryan-c on Thursday April 02, 2015 @11:33AM (#9311305)
LUKS supports encryption of block devices. Linux has robust support for using regular files as block devices via the loopback driver, so you can have a file as an encrypted container just fine.
Re:Truecrypt report by 0x0 on Thursday April 02, 2015 @11:30AM (#9311276)
Surely you can use LUKS on a loopback device backed by a single file?
Re:Truecrypt report by krylon on Thursday April 02, 2015 @11:49AM (#9311429)
I did so before moving to TrueCrypt. Mounting and dismounting was a bit convoluted compared to TrueCrypt (or encfs), I remember I wrote a Python script to make it a little more convenient.

But it did work fine about five years ago, and I do not think the situation has become worse.

Re:Truecrypt report by ryan-c on Thursday April 02, 2015 @03:44PM (#9312721)
From http://manpages.ubuntu.com/manpages/trusty/man5/crypttab.5.h...

    The second field, source device, describes either the block special
    device or file that contains the encrypted data. Instead of giving the
    source device explicitly, the UUID is supported as well, using
    UUID=<luks_uuid>.
That covers the init scripts, and it looks like recent versions of cryptsetup will "do the right thing" if pointed at a file rather than a block device.