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

am 85a1c578: Merge "Doc change: Adjust security sandbox description." into froyo

Browse Source 
Merge commit '85a1c578300a0c9fb23aef5f79c9b1f3892e9c2e' into froyo-plus-aosp

* commit '85a1c578300a0c9fb23aef5f79c9b1f3892e9c2e':
  Doc change: Adjust security sandbox description.
This commit is contained in:
Dirk Dougherty
2010-06-03 12:58:35 -07:00
committed by Android Git Automerger
parent c40209ac60 85a1c57830
commit b85a1679a4
1 changed files with 8 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/html/guide/topics/security/security.jd
View File

@@ -40,15 +40,14 @@ includes reading or writing the user's private data (such as contacts or
e-mails), reading or writing another application's files, performing e-mails), reading or writing another application's files, performing
network access, keeping the device awake, etc.<p> network access, keeping the device awake, etc.<p>
<p>An application's process is a secure sandbox. It can't disrupt other <p>An application's process runs in a security sandbox. The sandbox is designed
applications, except by explicitly declaring the <em>permissions</em> it needs to prevent applications from disrupting each other, except by explicitly
for additional capabilities not provided by the basic sandbox. These declaring the <em>permissions</em> they need for additional capabilities not
permissions it requests can be handled by the operating in various ways, provided by the basic sandbox. The system handles requests for permissions
typically by automatically allowing or disallowing based on certificates or in various ways, typically by automatically allowing or disallowing based on
by prompting the user. The permissions required by an application are declared certificates or by prompting the user. The permissions required by an
statically in that application, so they can be known up-front at install time application are declared statically in that application, so they can be known
and will not change after that.</p> up-front at install time and will not change after that.</p>
<a name="signing"></a> <a name="signing"></a>
<h2>Application Signing</h2> <h2>Application Signing</h2>