› Forums › Submission Queue › Cryptonite
This topic contains 15 replies, has 9 voices, and was last updated by krt 2 years ago.
- AuthorPosts
- February 28, 2012 at 7:50 pm #1542
Cryptonite is an EncFS implementation on Android. I’ve uploaded a repo directory for your review.
May 31, 2012 at 9:38 am #2011This is good.
August 10, 2012 at 2:30 pm #3022August 12, 2012 at 11:52 am #3041+1
August 12, 2012 at 1:52 pm #3043There 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.
August 26, 2012 at 4:18 pm #3347homepage: 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.
August 26, 2012 at 6:33 pm #3358yes, this would be the ideal (i don’t use dropbox)…
August 29, 2012 at 7:55 pm #3508I 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)
August 29, 2012 at 8:14 pm #3509An 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.
July 5, 2013 at 5:13 pm #7822It builds with a standalone toolchain (there’s a script in the NDK for creating one) and there are a lot of scripts to download and build the extra bits and pieces. Doesn’t seem to be too complicated , unless there are hidden dependencies.
October 2, 2013 at 7:48 am #8860I’d love to see cryptonite included – does a comment count as a vote, or have I missed something?
I came here from this page on their website: cryptonite
Thanks,
Rich
June 25, 2014 at 11:20 pm #11557+1
Also would love to see it included, even (and preferably) without Truecrypt and Dropbox support. I think what interests most of us here is the EncFS support.
October 25, 2014 at 6:48 am #13026I would also like to express my support for this app. I haven’t used TrueCrypt yet but i have been thinking about it for some time now. Having the capability on the phone sounds very nice. Including a crippled/stripped down version of cryptonite in f-doid is not very useful in my opinion.
October 25, 2014 at 1:00 pm #13039In contrast to Cryptonite readme, you cannot “vote” for it to be included. +1 gets you nowhere, merge requests and patches do. I, myself, would really love to see it in fdroid, but there is no space left on my todo list…
Github: https://github.com/neurodroid/cryptonite
Instructions: https://code.google.com/p/cryptonite/wiki/BuildInstructionsMay 10, 2015 at 12:19 am #15731Why is it removed from the repository? :/
- AuthorPosts
The forum ‘Submission Queue’ is closed to new topics and replies.
