Comments for Jan-Krueger.net

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Cchild

Cchild — Wed, 23 Jul 2008 19:58:02 +0000

Reinstall should not be a problem–My data is backed up. I may hay a handful files in my Windows home directory that I will lose.

This is how it happened. I was upgrading (clean install) from openSUSE 10.3 to openSUSE 11.0 and forgot one crucial check–I forgot to tell the boot-loader not to allow writing mbr to disk–since grub currently does not support truecrypt boot-loader.

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Jan

Jan — Wed, 23 Jul 2008 19:49:13 +0000

I’m not a certified expert or anything but yes, that’s what it looks like to me.

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Cchild

Cchild — Wed, 23 Jul 2008 19:48:22 +0000

So in other words, I must reinstall the OS?

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Jan

Jan — Wed, 23 Jul 2008 19:46:35 +0000

Bad news, I think: using another rescue disk to restore the bootloader trashes the volume master keys (every rescue disk has a copy of the volume-specific encrypted header, so using the wrong rescue disk restores the wrong header and the wrong keys).

I think you’re *really* screwed now. If so, you have my sympathy.

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Cchild

Cchild — Wed, 23 Jul 2008 19:42:06 +0000

I noticed the post on the forum was removed–and I figured it was probably due to naming.

It looks as if I may have to reinstall windows–the only other rescue disk I have is for another system. I used it to restore the truecrypt boot-loader, but it won’t accept my password. I will subscribe to your blog and maybe shoot you an email.

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Jan

Jan — Wed, 23 Jul 2008 19:33:26 +0000

No, that means something doesn’t work correctly but my error handling isn’t good enough to properly tell you what it was (sorry). Please send me an e-mail or subscribe to the blog feed to hear about updates. I’ll have another look at it tomorrow or so.

In the meantime, you can do the -DDEBUG recompile I suggested above to get a bit more information about where it fails.

PS. the name of the tool needed to be changed due to trademark issues; I have taken the liberty to slightly edit your comment to reflect this.

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Cchild

Cchild — Wed, 23 Jul 2008 19:29:12 +0000

# ./dmsetup-tc /dev/sda /dev/sda1 | dmsetup create foobar
Enter passphrase for encrypted volume:
dmsetup-tc: fatal error: Success

The above means it works correct–at least creating the mapper device?

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Jan

Jan — Wed, 23 Jul 2008 19:28:34 +0000

Things may be salvagable with dmsetup-tc IFF you didn’t overwrite too much. The volume header resides in sector #62; dmsetup-tc should be able to mount the partition if that is still untouched.

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Jan

Jan — Wed, 23 Jul 2008 19:27:03 +0000

This is a bit inconvenient as a chat system, isn’t it? ;)

If it dies without an error message or anything like that, it may be helpful to compile it differently: change the CFLAGS line in Makefile to CFLAGS = -O3 -DDEBUG and re-run make.

If something doesn’t work right, you’ll need to be a bit more specific.

Comment on How to use TrueCrypt®-encrypted Windows system drives on Linux by Cchild

Cchild — Wed, 23 Jul 2008 19:24:57 +0000

I mistakenly override the truecrypt boot-loader and the rescue disc to my foolishness is an image file located in my documents directory in windows, the drive that is fully encrypted.