Notices

So, how do I know which version of kernel power is installed?
Sorry, I took the TrueCrypt link from the page I saved.
I think it was the one you posted in the first post of this topic.

I had this error trying to mount volume with ext4 filesystem.
I had to manually specify filesystem
Try adding --filesystem=XXX to the truecrypt command (where XXX is the FS in the truecrypt volume).

You can also decrypt the volume without mounting using --filesystem=none , and mount manually using mount command

uname -r. And please, next time do your research on such simple questions. So, what cipher are you using for that volume?

I am using version 7.1. Estel's wrapper keeps telling me xts is not supported and keeps setting -nokernelcrypto

But I'm using KP49 - is there anything else I need to add or enable for kernel crypto to work?

nman, are you executing everything as a root? Otherwise, I haven't seen any situation, when it would fail to detect XTS support using latest (repositories) kernel.
---

If it isn't source of Your problems, a dirty workaround would be to set up Your custom small script, that does:
... and run truecrypt.real (actual binary) after that. This way, You do exactly what wrapper does for You, *except* the part checking for kernel support and setting '-m nokernelcrypto' otherwise.

Just be sure, that You *really* have proper kernel with proper support. You can cat /proc/crypto to see supported modes. If any of things listed there got XTS in name, you're good to go.

/Estel

Did you install the kernel-modules package as well? KP49 is pretty good about having most things built in, but this particular thing is a module. If you installed just the kernel and not the modules, and don't use some of the other advanced things (like h.e.n.) you may not have noticed that till now.

IIRC, It'll only appear there if it the module is loaded. Thus, the best way to check is to take a look at /lib/modules/`uname -r` or to load it with modprobe.

Thanks, I have modules installed...
No I wasn't running TC as root - when I do I don't get the error message from the wrapper.
Looks like that was it, but... when I run TC benchmark, results are the same.

I don't see xts when I do cat /proc/crypto...

nman, as stated on the first page, you *must* run truecrypt as a root. Benchmark won't show the difference, but trust me, You'll feel it on real volumes, in form or "goddamnit" errors, as truecrypt normally expect XTs support.

/Estel

Thanks, working great.
And holy carp what a difference - copying 2GB file to encrypted partition, as user - 28minutes.
as root, presumably with kernelcrypto - 2 minutes!!! (which works out to about 20Mb/sec, about the same as for unencrypted copying!

Just side note in my defense Nothing on the first page about running as root...(maybe there is in other thread started by Estel).. might want to add that in. (or merge the threads...)