Yes I agree, but my point is not to complete all the weaknesses of Android in terms of privacy. I have made with some colleagues a dependency-aware privacy management model for mobile applications. And I'd like to focus on those dependencies so I'd like to use that kind of tool to make some observations, not to build anything. I'll not detail this here but our idea cover some privacy issues of the current system. The prototype part will only be a tool to add applications to groups and privacy constraints over permissions granted to those groups and not to applications directly, using a right expression language. Then tools for privacy management could use this policy database on each device.
On Sat, Dec 4, 2010 at 7:11 PM, Chris Stratton <[email protected]> wrote: > On Dec 4, 12:34 pm, guillaume benats <[email protected]> > wrote: > > > Right, I could use tool like TaintDroid or ScanDroid if they were > > publicated... > > I strongly suspect that there are ways to leak private information > which such tools would be unable to identify or distinguish from > innocent transmission of non-private data. > > Further, they cannot prove an application safe - they can only have > not yet detected that it's done something evil. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Benats Guillaume . -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
