Of Truecrypt and how to screw things up…

I’ve been using TrueCrypt from quite a long time now. I’ve always been impressed by its ease of use and, most important, the chance to use it both on Window$ and GNU/Linux systems, bot desktop and server/remote systems.

So, when version 5.0 was released a couple weeks ago I was excited about the new release. One of the most interesting features was the disappearance of the kernel modulo, no need to recompile it after any kernel upgrade! :)

But, there’s always a “but” laying around, the happiness vanished pretty soon! :(

First of all I discovered that even to sue text mode GTK libraries are required. Why should I have unneeded garbage on a server? Who knows. Then came out that tou cannot create encrypted containers from command line (no -c option) which definitely killed any hope to use it on a remote system.

So basically I now have 2 choices: keep using 4.3a version (compiled from sources, since .deb package oddly enough seems to be Ubuntu only, and not working on my Debian Etch boxes) or move to another encrypted filesystem (LUKS? perhaps).

What I’d love to ask to TC developers is: how can you do such a dumb move? :|

Le ultime news da linuxSecurity.it: