TrueCrypt 7.0 released, now with hardware-accelerated AES support
truecrypt.org
truecrypt.org
For FOSS-champions thing is that TrueCrypt developers are sneaky and don't accept contributions, so that in practice there is little outside control, and "given enough eyeballs are bugs are shallow" doesn't quite work.
For technical users, admins and frugal geeks TrueCrypt hides several unpleasant surprises, such as the encryption being undoable without a huge spare disk.
For casual users interface is cumbersome and counter-intuitive at times. It's almost as if developers have never considered usage scenarios. You have to type your passwords more often than strictly necessary, and sometimes you have to remember to do it, with risk of losing your data.
(If you look at Wikipedia's crypto-disk-software comparision page, http://en.wikipedia.org/wiki/Comparison_of_disk_encryption_s..., you'll see that dm-crypt/cryptsetup/LUKS has pretty much all the features you would care about. Hidden containers would be nice, though.)
But I did some googling before hitting "reply", and apparently you can also mount dm-crypt volumes on windows with FreeOTFE. I guess I should have done some more research before switching.
If you're talking about an encrypted file container on a USB stick, the same problems exist with other encryption software. But I only remember typing in my password when mounting one, I'm not sure where it's asking you for your password over and over.
If you want a USB stick with decent usability, spend 99 bucks on an ironkey, and you'll get real hardware encryption as well.
Perhaps, or perhaps they just XOR your data with your passwd like a certain tape maker did for their super hardware AES mil-spec encryption.
https://www.ironkey.com/usb-flash-drive-flaw-exposed
Of course, like anything, they could have other unknown vulnerabilities. But like they say in the video on that link, they're a security company that makes a storage product, opposed to a storage company making a security product.
I laughed a bit thinking of extreme trade off in those two statements (so allow me to respectfully embellish [is that possible?]):
Security company makes a storage product: It's secure because they have no idea how to make a storage product and therefore your data is not actually stored anywhere that it can be retrieved in the event that you've provided the correct key.
Storage company makes a security product: The data is stored properly. It is then encrypted using whatever sample code was discovered in a search for the acronym "AES" with a bunch of redundancy in the event that something with the physical media fails. This redundancy is stored in the clear.
A vulnerability in storage results in inaccessible data. A vulnerability in security results in overly accessible data.
They accept contributions, you can even take the source and fork it. The only thing you can't do is call your version with added rootkit "Truecrypt"
System disk encryption in place is possibe and undoable. Data disks - I don't want to be able to do/undo this in place, I want them properly wiped.
You have to type in the passwd once to mount the disk? If you want to mount multiple disks with the same passwd (!!!) it will cache it
Edit: This is all common knowledge and has been for a few years. Wikipedia has all the details. The Czech Republic connection with the Trademark, the anonymous/unnamed developers, etc. The new (as of this year) mailing address in the US, the fake domain name registration, etc.
One last edit: TrueCrypt is probably fine protection against common thieves, but enough bits may have been knocked off of it to make it "acceptable" for export. If I was a Russian Spy, I would not touch it with a ten foot pole.
* Assuming the people behind it's development are doing so with a sketchy purpose...
They do now advertise a US address next to some Air Force base in Nevada.
The address listed on their website appears to be an office in a pretty mundane Vegas suburb, surrounded by restaurants and small businesses. Am I missing something?http://maps.google.com/maps?q=375+n.+stephanie+st.+suite+141...
Example supported processors include (select) ones from the i5/i7 desktop and mobile Intel processors, but anything which has that instruction set should work, apparently.
(from: "hardware acceleration" chapter, link near the top of the article)