res->size = 128;

should be

res->size = 64;

Am I right ? (Has no effect though, since “size” is never used again here as far as I can see … )

first off, you do know that the name you filled in there is a bit confusing, right? ;)

Anyway. tc-dmsetup currently doesn’t support “normal” TC partitions. I wrote it when TC for Linux did not support mounting Windows encrypted system drives *at all*. Now that it does, perhaps I should extend tc-dmsetup to handle the normal case too. Patches welcome, of course.

As for accessing TC-encrypted ext2/3 partitions from Windows, I have no idea. On my computer I have avoided doing that because I didn’t want to ask myself that question. In theory it should work a bit like this: TC handles the decryption stuff and designates a drive letter to use and for accessing the filesystem the ext2 driver automatically kicks in. One thing that may or may not help is trying a different ext2 driver, e.g. Ext2fsd.

Good luck!

also, for a related problem – when I boot into my windows side, how do I r/rw my TC partition linux formatted in ext2fs? I used ext2ifs before but now that the partition is encrypted and in ext3, neither truecrypt(windows) nor ext2ifs can deal with it.

Here is the solution, it was very simple: My kernel was simply lacking XTS crypto support, even though the error message given by dmsetup did not give any indication of that at all. You might wanna mention that in the program requirements, though. My current kernel (2.6.25) still has XTS marked as Experimental, but my previous one (.23) didn’t have it at all. So, I guess I am not the only one out there that need to do a kernel update for that. For completeness sake, my system has both the regular loopback device as well as the device mapper crypto target (not the crypto-loop device) coded into the kernel and this works just fine with multiple encrypted volumes. Adding an abitrary number in form of encrypted USB disks seems to work, too. So, I guess there is no limitation.

Once again I wanna thank Jan for this wonderful tool. I have it running on two computers now, without any problems, and I still keep using it in spite of the new TrueCrypt version claiming to offer the same functionality. I just like the slickness with which it perfectly integrates into my automount scripts. Contrary to this, I HAVE to use the official TC for my non-System windows drives and the way it messes up my mtab with those weird fuse mounts is just bad and not pretty at all.

Finally, Jan’s program came in very handy when I was struggling to understand the TC Volume Specification, in order to make a low-level backup of all my MBRs, partition tables and crypto headers. Btw, I recommend doing that to everyone, in DMCrypt+Luks the single availability of the header is the single point of failure and TC only has the backup burned to the Rescue CD (apparently, there is no backup volume header on the driver for system encrypted drives).