3 ms·

I did something quite similiar last summer - we got it published (http://www.cl.cam.ac.uk/~arb33/papers/BeresfordAREtAl-MockDroid-HotMobile2011.pdf http://www.c

I did something quite similiar last summer - we got it published (http://www.cl.cam.ac.uk/~arb33/papers/BeresfordAREtAl-MockDroid-HotMobile2011.pdf http://www.cl.cam.ac.uk/~arb33/papers/BeresfordAREtAl-MockDr...) but we never looked at getting it into CM. I guess they're more receptive to the idea than I expected them to be! The whole faking data thing works quite well - every app we tried with our implementation basically worked as intended (i.e. if you prevent the app from accessing the internet, everything still works apart from functionality which explicitly depends on accessing the internet), which is a nice consequence of apps being written for mobile devices where access can't be taken for granted.

mdwrigh2 15y ago
I find it interesting (but not all that surprising) that so many people developed a similar concept. The research professor I was working with this past year actually published a similar system: http://www.csc.ncsu.edu/faculty/jiang/pubs/TRUST11.pdf http://www.csc.ncsu.edu/faculty/jiang/pubs/TRUST11.pdf
- njs12345 15y ago
  That does look pretty similiar to what we did. I've emailed Plamen about it - hopefully we can integrate all this stuff to give CM users full control over what apps do with their personal data :) TaintDroid is pretty awesome as well: http://www.appanalysis.org/ http://www.appanalysis.org/