You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: