Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Info on two special (more-than-'dangerous') permissions

Browse Source 
There are a couple of 'signature' permissions that have a special
user-authorization process; mentioned them and put in a link to their
reference docs.

The reference docs for those methods is being updated in a separate
CL, http://ag/784299

See first comment for doc stage location.

bug: 24673125
Change-Id: I4f17784b570d6154482e3fe965bd2de1043babb6
This commit is contained in:
Andrew Solovay
2015-10-07 13:40:04 -07:00
parent ac2be1998e
commit 3915a0e83a
1 changed files with 23 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/html/guide/topics/security/permissions.jd
View File

@@ -305,6 +305,29 @@ to be as high as possible. You can see which permissions were added with each re
</li>
</ul>
<div class="sidebox-wrapper">
<div class="sidebox">
<h3 id="special_permissions">Special Permissions</h3>
<p>
There are a couple of permissions that don't behave like normal and
dangerous permissions. {@link android.Manifest.permission#SYSTEM_ALERT_WINDOW
SYSTEM_ALERT_WINDOW} and {@link android.Manifest.permission#WRITE_SETTINGS
WRITE_SETTINGS} are particularly sensitive, so most apps should not use
them. If an app needs one of these permissions, it must declare the
permission in the manifest, <em>and</em> send an intent requesting the
user's authorization. The system responds to the intent by showing a
detailed management screen to the user.
</p>
<p>
For details on how to request these permissions, see the {@link
android.Manifest.permission#SYSTEM_ALERT_WINDOW SYSTEM_ALERT_WINDOW} and
{@link android.Manifest.permission#WRITE_SETTINGS WRITE_SETTINGS} reference
entries.
</p>
</div>
</div>
<h3 id="perm-groups">Permission groups</h3>
<p>