Neural Interface

Ich habe jetzt TrueCrypt runter geladen und installiert. Innerhalb von 3 Stunden Beschäftigung mit der Mac OS X Version habe ich 4 Bugs gefunden. -.- Ich werde die mal reporten und dann ma schauen, was das allgemeine Feedback ist.

Edit:

Found some more ;)

Bugs with TC43a encrypted devices:
——————————————————

Bug 1:
“Mount All Devices”
TC5 stalls, high CPU Usage, freezes, has to be force quieted.

Mount All Devices is not really a feature in this version. Consider to not provide it and blank it out. It has a very high frustration factor!

——–

Bug 2:
“Mount Device”
Short, high usage of CPU, Permission denied on all access except viewing (reading not possible).

This is a very strange bug. The devices are FAT32 formatted, so no permission should be implemented. Yet, Finder, VLC and mplayer report that they have no permission to read (e.g. play a file), yet reading is possible (e.g. browsing files).

THIS BUG OCCURS ALSO IN TC5, BUT IS NO THAT OFTEN. With TC4a devices, this was 100% reproducible for me.

——–

Bug 3:
“Broken Pipe” message on Dismount.
Not really a bug, just a annoying error message. Please provide a meaningful message here. I can’t fidre out, what I did wrong here ;)

——–

Bug 4:
Copy stalls with Error in Finder.
While copying from an unencrypted device to an encrypted device with Disk Order (which uses the Finder functions), the Disk Order App stalls, freezes and the copy process does not go on, while the finder becomes unresponsive and has to be foce quitted.

POSSIBLE DATA LOSS! The last copied file was not existent on the destination device (here no problem, but maybe with move).

Bugs with TC5 encrypted devices:
——————————————————

Bug 5:
Mount failed: “hdiutil: attach failed – no mountable file system”
When mounting an encrypted device, it fails with the above message. Partly, this is due to some boot behavior of Leopard.
E.g.: When rebooting with an encrypted USB Flash Drive, Leopard will display an error message about the non usable file system on the Drive. Click Ignore. Mounting with TC5 will fail with above message.

Solution: Plug it out – Plug it in. Mounting will be possible in 80% of the cases!
Maybe, we can write a routine into Mac OS X to ignore certain drives on boot dynamically.

Bug 5.1:
As above, but with internal partitions on the startup disk. The problem here is, that you can not unplug the partition ;)

Possible solution, not yet tested (I can’t find the UUID):

http://www.macosxhints.com/article.php?story=20060930150059172

This makes TC5 unusable for cross platform encryption on internal hard disks. Sad but true :-/

Bug 6:
Usability improving please!
If I want to make an encrypted file, using an FAT32 partition, TC5 fails with the message “File too large”. This is soooo idiotic ;) Please, just write what the maximum file size is _before_ you create it (e.g. in the dialog where you choose to use FAT32). This is very simple and avoids much frustration on the user side! :)