Closed neurodroid closed 10 years ago
From n...@google.com on November 27, 2012 13:18:14
truecrypt team: Please try recompiling your app with Android NDK r8b or greater. This will fix this bug.
From christoph.schmidthieber@gmail.com on November 27, 2012 13:22:12
Thanks for the report, and thanks for suggesting a fix. Will rebuild with r8c.
Status: Accepted
Owner: christoph.schmidthieber@gmail.com
Labels: -Priority-Medium Priority-High
From christoph.schmidthieber@gmail.com on November 27, 2012 13:38:37
@anilkpatel: Could you test the encfs binary that ships with 0.7.6? It's been built with r8c and shouldn't produce this error. TrueCrypt had to be built with Crystax NDK 7 because of incomplete wchar support in the official NDK. It's a known problem: http://www.crystax.net/trac/ndk/ticket/112 If it can't be resolved on the Crystax side, we'll have to switch to the official NDK and find a wchar workaround.
From anilkpa...@gmail.com on November 27, 2012 13:43:11
On testing the encfs binary on 0.7.6, here is what I did:
RESULT: Got the encfs usage message. In other words, the linker error that I saw using the truecrypt binaries is not present with encfs.
Let me know if there are additional steps you want me to try. I appreciate your help.
From christoph.schmidthieber@gmail.com on November 27, 2012 13:46:05
Thanks for your quick test. We'll have to wait for a reply from the Crystax team now.
From christoph.schmidthieber@gmail.com on November 27, 2012 18:40:56
This issue was closed by revision 63b3b3366cde .
Status: Fixed
From christoph.schmidthieber@gmail.com on November 27, 2012 19:08:15
Try the latest truecrypt binary, available from the downloads section: https://code.google.com/p/cryptonite/downloads/list
From anilkpa...@gmail.com on November 27, 2012 19:59:46
The new binary works. The linker error is gone. Thanks for the quick turnaround! Now I have a different error with the mounting, but I can open another issue for that.
From christoph.schmidthieber@gmail.com on November 27, 2012 20:29:00
Yes please.
Status: FixVerified
From christoph.schmidthieber@gmail.com on November 28, 2012 06:11:52
Do you have a "mount" command sitting in /system/xbin/mount? If not, try to install BusyBox from the Play Store.
From anilkpa...@gmail.com on November 28, 2012 12:35:02
Yes, I have a mount command in /system/xbin/mount. This is linked to my busybox mount. The mount was failing because I had not created the target mount directory first. Once I did that, the mount succeeds. However, there is an issue with limited file accessibility. I've created issue #47 to describe it.
From christoph.schmidthieber@gmail.com on February 24, 2013 13:25:42
Issue 50 has been merged into this issue.
From anilkpa...@gmail.com on November 25, 2012 00:42:01
What steps will reproduce the problem? 1. Launch terminal with Expert->Start root terminal
Original issue: http://code.google.com/p/cryptonite/issues/detail?id=46