search

neurodroid / cryptonite

EncFS and TrueCrypt on Android
GNU General Public License v2.0
203 stars 49 forks source link

Very weird that non root apps' accessibily to mounted data is very random #64

Open neurodroid opened 10 years ago

neurodroid commented 10 years ago

From zcn...@gmail.com on October 09, 2013 06:08:46

Some apps can access the mounted data, while some can't Sometimes some apps can, but after a while, they can't

All I tested are non root apps

Why this weird result?

Why some apps can, while others can't?

Why sometimes can, while sometimes can't?

Original issue: http://code.google.com/p/cryptonite/issues/detail?id=64

neurodroid commented 10 years ago

From loic.lem...@gmail.com on December 04, 2013 01:49:33

What I said in issue 47 may help:

On my Galaxy S4 (stock ROM I9505XXUBMGA, Android 2.2), I've noticed that only apps that are loaded in memory before the mount could see the content of the crypted volume. So I start all apps that I would use (Text Editor, File Browser, etc.) and press the Home button to put apps in background without exiting them. Then I mount my crypted volume, and I could use file on the crypted volume in any apps I previously launch.

I'm using cyrptonit 0.7.9 (alpha) as I discovered this behavior after uninstalling the stable release on the Play Store, thinking that the stable version don't work. Later trying the alpha release, I found this workaround, but it probably works on any cryptonite version.

neurodroid commented 10 years ago

From djnutz on February 22, 2014 14:22:17

Same issue.

dimovnike commented 9 years ago

Same issue. Im running the encfs binary from adb shell and some apps see it some dont. My goal is to always run encfs on startup (probably via SManager) with --reverse option and sync the encrypted files to cloud (not dropbox, some other less popular app). Also the @neurodroid remark is correct. I had Total commander running before I mounted the dir and it saw the files, also the updates. After killing it and restarting - no more files. What would be the correct way to solve this?

dimovnike commented 9 years ago

from what i understand this happens because of the new multi-user Android feature. They use different mount namespaces, but how the command setns doens't work on this kernel...