![]() |
Re: EasyCrypt Frontend for TrueCrypt
Ya, I put them in a startup script in /etc/init.d I think so that they install at every boot.
BTW sorry for the lack of updates, but has anyone tried either EasyCrypt or TC5.1a in Diablo yet? I've been working on some other stuff and haven't gotten around to trying a Diablo upgrade on any of my IT's yet. |
Re: EasyCrypt Frontend for TrueCrypt
Quote:
It just won't check if the card is actually inserted...that's the same as the N800 but for both card slots. Sorry if I confused anyone before :) |
Re: EasyCrypt Frontend for TrueCrypt
I've already put the insmods in a startup script and that works fine.
There was no confusion with the device names. I do find that, after using EasyCrypt to mount the volume on /media/mmc1/secure, I then have to mount the partition separately using: mount /dev/mmcblk1p2 /media/mmc1/secure. This is because, when I try to mount a volume in EasyCrypt, choosing the device doesn't work for me - I can only do it by opening the crypt.tc file. It doesn't sound quite like your notes suggest, but it's working. The other problem I still have is that, if I try connecting the N810 to an XP box via USB and then try to mount the drive using TrueCrypt, it gives me a blue screen of death on XP. The only way round this is to mount the volume on the N810 and then use WinSCP to get the data. Paxton P.S. Still using TC 4, cos I'm not brave enough |
Re: EasyCrypt Frontend for TrueCrypt
Quote:
Quote:
|
Re: EasyCrypt Frontend for TrueCrypt
Quote:
LUKS + dm-crypt might also be an option. Its GPL and compatible with FreeOTFE provided your OS has a driver for the filesystem. Ext2 drivers exist for Windows. |
Re: EasyCrypt Frontend for TrueCrypt
I have an 8MB vfat partition on the external memory card and the rest set up as an ext2 partition. I used GParted on Debian to set these up, but had to do a mkfs.vfat to format the small partition, as GParted doesn't have that option.
I just checked on the TC on my XP box and that is 5.1a, so I need to get them both up to 5 to avoid the blue screen problem. I am using Ext2 IFS on XP btw. Thanks for that - I will upgrade to TC 5 when I get a chance. |
Re: EasyCrypt Frontend for TrueCrypt
Quote:
Seems to work nicely and now has the ability to hide the real OS and create a decoy OS. So if you are ever forcibly coerced to boot the OS, based on the password you issue at the pre-boot screen, you can boot the decoy and not reveal the real OS. I'll try to recompile 6.x for Diablo soon and see what happens :) |
Re: EasyCrypt Frontend for TrueCrypt
Plausible deniability broken in non-full disk encryption. Glanced a bit through it; doesn't seem rocket science, but something to keep in mind. 6.0a might fix some of the described issues.
|
Re: EasyCrypt Frontend for TrueCrypt
Ok I've compiled 6.0a for Maemo and tested with Chinook. Gotta get off my arse and install Diablo and test on that too.
Running in Chinook seems to work ok but generates some warnings about using a pre-2.6.24 kernel and also that opening a container made with any TC prior to 5.0 may exhibit poor performance. TC6.x now has the ability to load balance the encryption overhead across multiprocessor/multicore systems. Guess N8x0 users don't need to worry about that for now. Definitely seems to make a difference on my Core2Duo laptop though. I have posted the binary on my web site. http://www.securix.net If you test it, let me know how it goes.... |
Re: EasyCrypt Frontend for TrueCrypt
Great!
I'm not using this program myself (yet). Maybe its easier (read: faster on CPU, resource wise?) to have an encrypted storage online on a server, and use VPN, SSHFS or such to access it (preferably with SSH keys, or S/Key or OPIE). This way, there isn't much to lose when the device is lost either, and furthermore there is no need for plausible deniability. I'm not trying to belittle your work, just stating a possible alternative :) |
| All times are GMT. The time now is 02:10. |
vBulletin® Version 3.8.8