Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDroid Permission #53

Open
mateor opened this issue May 22, 2013 · 0 comments
Open

PDroid Permission #53

mateor opened this issue May 22, 2013 · 0 comments

Comments

@mateor
Copy link
Owner

mateor commented May 22, 2013

I am thinking we should add a PDroid Permission to the core and apps. I don't want it to entitle any access to the API, but more be a simple boolean requirement for the core.

Honestly, I don't want it to expose any functionality, but to merely be added to all available PDroid Management apps in the permission lists, so that there is a big red flag if this permission is ever requested (perhaps color those apps red in the manager app list?).

This is a solution to the eventual issue of an attack app bundling PDroid API into it's framework. An earlier suggestion was to hardcode in all known package names but that was met with a tepid response. But that is what CollegeDev has done for PDroid2.0 1.54, and I think this might be a compromise.

Any thoughts out there? This is inspired by koush's very sensible introduction of the Superuser permission, but is a relatively recent idea.

Edit: The docs on this and some cautions about the process are here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant