maemo.org - Talk - EasyCrypt Frontend for TrueCrypt

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - EasyCrypt Frontend for TrueCrypt (https://talk.maemo.org/showthread.php?t=15984)

Re: EasyCrypt Frontend for TrueCrypt

Hmm, it's possible I need to require e2fslibs as a dependency as well. I thought they automatically install as a dependency to e2fsprogs but I might be wrong.

Try installing that too (apt-get install e2fslibs) and see if it works.

The specific files I used are:

e2fslibs_1.37-2sarge1_armel.deb
e2fsprogs_1.37-2sarge1_armel.deb

The only additional repository sources I have in my /etc/apt/sources.list are:

deb-src http://repository.maemo.org/ chinook free non-free
deb http://repository.maemo.org/ chinook free non-free

Re: EasyCrypt Frontend for TrueCrypt

Quote:

Originally Posted by BoxOfSnoo (Post 170189)

I'm having a hard time installing because of its dependence on e2fsprogs. I can't install this because it says libcomerr2 is not installable. I don't have any Ext2/3 containers, only vfat ones. Is there some way to get this all happy?

Is there a repo I'm missing?

Did you check gronmayer?

Also, Red Pill may be required to see/install that lib.

BTW, coincidentally, those files can be downloaded and installed if you selectively follow Steps 4 through 6 of the cloning guide in my sig.

Re: EasyCrypt Frontend for TrueCrypt

No, I have e2fslibs installed ok. e2fsprogs is the problem.

Maemo repository is being useless again. I changed to "reposiory" and it is downloading now.

I sure hope they learn about caching proxies before diablo comes out.

Re: EasyCrypt Frontend for TrueCrypt

I have just posted a new easycrypt-maemo update, 0.2.2.5d on www.securix.net.

This version now has the ability to open mmc/SD card device volumes. The volume can be an entire SD card or any of 4 partitions. I also included the stat binary that was confounding a few people before.

However, the formatting of a device partition must be done from the command line or externally on a computer with a device reader, etc using sfdisk. EasyCrypt does not have a facility to do this yet.

Remember that if you format an entire SD card as a Truecrypt device, Maemo will report the card as being corrupted. If you're OK with that (or know how to turn off the nagging) then you can use the entire card. Otherwise, you can format a few blocks of partition 1 as an msdos (FAT16) volume so Maemo sees it, then create a directory mount pont for convenience (of course you can mount the device on any directory mount point you like). Then you can format the rest of the card as a Truecrypt volume using any filesystem you want (vfat, ext3, etc). And yes, while you're at it, you can create a hidden volume and you can use that too.

So for example, for a 2GB SD card, 10 blocks of /dev/mmcblk1p1 are formatted as FAT16 and /dev/mmcblk1p2 represents the remainder of the card and is formatted with Truecrypt. Then use EasyCrypt to open /dev/mmcblk1p2 as a Truecrypt volume and mount it anywhere you like.

So effectively, you can also unmount and remove the SD card and plug it into an external USB reader on another Windows or Linux system and mount it with Truecrypt as well. Nice.

Just be careful because EasyCrypt does not yet check if you're using an N800 or N810 and does not hide the fact that the N810 only has one mmc slot - and will show options for both slots regardless.

Hopefully people will find all this stuff useful. Please drop me a line with any questions, bugs, etc....

Re: EasyCrypt Frontend for TrueCrypt

where is the crypt file in the normal mode? what is the name?

The reason I ask is when switching to expert mode I'd like to be able to select that default crypt file. Sorry for being lazy to dig it up in the code. :D

Re: EasyCrypt Frontend for TrueCrypt

Quote:

Originally Posted by nhanquy (Post 179728)

Hehe well, it's actually described in the INSTALL.txt file on my web site too:

When EasyCrypt is first executed, it will show a welcome screen indicating that it will run in NORMAL mode by default. In normal mode, EasyCrypt will create a hidden .config directory in /home/user in which to store the configuration file.

It will also ask if you want to set up a default crypt file. This crypt volume container will be a file in /home/user called .easycrypt-crypt. The default crypt container will be formatted as a FAT (MSDOS) file system. Once built, the default crypt volume not mount on its own. To mount the crypt, select the "Mount the crypt volume" from the menu. In Normal mode, the crypt file will mount on the /home/user/MyDocs/EasyCrypt directory.

Hope that helps...

Re: EasyCrypt Frontend for TrueCrypt

Quote:

Support for Truecrypt 5.x whenever it can be compiled for Maemo.

Wish granted.

http://www.mediafire.com/?jmcyjjhjzw2

Just binary of 5.1a.
V5 uses FUSE. I made sure it compiled without the GUI but it *may* (most likely not) ask for wXwindows. There is a port of FUSE on this forum. I had to compile my own however but it was clean compile of same version so nothing should differ.

Re: EasyCrypt Frontend for TrueCrypt

Your 5.1a binary does the same as mine has been doing since I first tried 5.1a back in March, which is why I kinda put it on the backburner.

Code:

Nokia-N800-50-2:/media/mmc2# /home/user/truecrypt tcvol secure

Enter password for /media/mmc2/tcvol: 

Enter keyfile [none]: 

Protect hidden volume? (y=Yes/n=No) [No]: 

terminate called after throwing an instance of 'TrueCrypt::SystemException'

  what():  TrueCrypt::FilesystemPath::GetType:30

I compiled my own fuse libs based on 2.7.2 and then tried Ukki's based on 2.7.3 but the same thing happens.

Also, when I compile 5.1a, I get a strange error about testing right after linking finishes...

Code:

Linking truecrypt

terminate called after throwing an instance of 'TrueCrypt::TestFailed'

  what():  TrueCrypt::PlatformTest::TestAll:202

qemu: uncaught target signal 6 (Aborted) - exiting

make[1]: *** [truecrypt] Error 126

make: *** [all] Error 2

But the actual compile finishes. Apparently the make script runs some self-tests at the end, which is what's failing.

I set up SB2 recently so I could try compiling with gcc 4 but haven't really had much time to mess with the whole thing.

But if yours is working, then there's something flaky about my N800's setup...any ideas?

Re: EasyCrypt Frontend for TrueCrypt

Hmm, I have to admit I never really tried out the binary :/

(Yes, kill me now)

I thought it would work after being compiled. I did it in a SBOX1 with better ARM emulation. I'll set up sbrsh sometime and compile it on my N800.

I got the same error but if the binary was compiled... :/

My apologies.

Re: EasyCrypt Frontend for TrueCrypt

I was hoping yours would work because it would save me going back to try to figure it out.

I tried other stuff like loading fuse.ko in a different order but that didn't work either.

I'm a little hung up on the TrueCrypt::FilesystemPath::GetType:30 error, which leads me to think it has something to do with FUSE or the use of /dev/loop instead of /dev/mapper.

Then again, the new 5.x rewrite of TC with its insistence on using wxWidges regardless of NOGUI is a little disturbing also. People on the TC forums have been begging for a "decoupled" version since it came out. It also seems people are seeing a little more of a performance hit over 4.3a in Linux as well.