Hacker News new | past | comments | ask | show | jobs | submit login

i was looking around to find lore regarding sandboxing android apps, so far i found this interesting:

https://www.reddit.com/r/androidapps/comments/5n7ak9/any_app...

And this too:

https://www.gtricks.com/android/how-to-sandbox-android-apps-...




As other commenters have mentioned, traditional sandboxing mechanisms would do little here. Applications are always given read access to system libraries because they need them to function.


im thinking about how we get to non traditional sandboxing


Here's a stupid idea I had elsewhere in the comments: https://news.ycombinator.com/item?id=20840466


i think one of the biggest nuts to crack is that end user is in app space and cant black list apps [such as FB] from system procs and resources. If we could sniff and/or hook for requests to read the entire library all at once, or for such a request from a particular app, and ~pihole it or give it a honeypot to suck on for data.


Fully homomorphic public key encryption is the solution. We need such a crypto that hides the instructions and operands but does not alter the visible arity of instructions, and allow arithmetic operations on operands.


Kiss your battery life goodbye then, because HE requires a massive amount of CPU power. So much that it's outright prohibitive for use on a cell phone for at least the next 5-6 years, minimum (Moore's Law)


Buy a second device. $100 will get you a good used phone, $50 a decent used tablet. Then you can segregate your own use, say making your primary device microg+fdroid, and only using the device with the surveillance culture apps where necessary.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: