Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
add support for disabling dangerous permission groups in legacy apps by default #260
Comments
thestinger
added
the
Type: enhancement
label
May 13, 2016
thestinger
added
the
project
label
Jun 12, 2016
thestinger
added
the
Language: Java
label
Jun 20, 2016
thestinger
added
the
Priority: low
label
Jun 23, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
#645 might be relevant, needs research |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Jul 2, 2017
Contributor
This is now implemented in a friendlier, enabled by default way via #645.
|
This is now implemented in a friendlier, enabled by default way via #645. |
thestinger
closed this
Jul 2, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
thestinger commentedMay 13, 2016
•
edited
Edited 1 time
-
thestinger
edited Jun 12, 2016
An attempt was made to implement this, but it didn't work properly the way it was done. It needs to be reimplemented.
It should set up the dangerous permission groups that are exposed in the UI to provide fake data. Using the new permission system for legacy apps is a bad approach, since it throws security exceptions. The changes would be in frameworks/base, somewhere in the package installation process.
A global property is likely the best way to expose this, since it's not really a per-user setting. Of course, the toggle should only be exposed to the owner user.