Cryptonite is an EncFS implementation on Android. I’ve uploaded a repo directory for your review.
There wiki on the project web page describes how to build it, but Im not sure if those native bits can be built. The truecrypt can be left out I think and the dropbox component may need a api key to work. The app functions fine without these and thats the best use for it, as protection against thieves who know how to boot into recovery and as an encryption for file synchronization. But then maybe the developer wouldnt be happy.
homepage: https://code.google.com/p/cryptonite/
issues: http://code.google.com/p/cryptonite/issues/list
Code license: GNU GPL v2 [no idea about TrueCrypt -- compile without if necessary]
Cryptonite brings EncFS and TrueCrypt to Android. You can browse, export and open EncFS-encrypted directories and files on your Dropbox and on your phone. On rooted phones that support FUSE (e.g. CyanogenMod) you can also mount EncFS and TrueCrypt volumes. TrueCrypt is only available as a command-line version at this time.
Cryptonite is available from Google Play. Report bugs to the issue tracker.
yes, this would be the ideal (i don’t use dropbox)…
I noticed they’ve got a link to this thread on their project page. Great to see that they want to get included! As i think it would be ideal to have one of the developers submitting the data we should have a document to point them to. It should explain how the build-server works and that unfree libraries have to be excluded. (Maybe more, I’m no dev)
An FAQ perhaps? The are many different reasons apps cant enter. In this case , having read the build instructions and not understood anything, the problem is technical. The first step requires the ndk be customized, which is only feasible with virtual machines and thats what we call the build server. This app is completely FOSS as far as I can tell. The dropbox integration is irrelevant: and in any case there is a step for disabling it.
