From 5bacbfd39ba71089f9d599e5954aaa7cbee630a7 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Wed, 2 Jun 2010 16:53:00 -0700 Subject: Doc change: Adjust security sandbox description. Change-Id: I7b2f530afe65fe0abe6c66e69c9abddcfbc5ae9c --- docs/html/guide/topics/security/security.jd | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) (limited to 'docs/html/guide/topics') diff --git a/docs/html/guide/topics/security/security.jd b/docs/html/guide/topics/security/security.jd index da201c4..dbc9866 100644 --- a/docs/html/guide/topics/security/security.jd +++ b/docs/html/guide/topics/security/security.jd @@ -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 network access, keeping the device awake, etc.

-

An application's process is a secure sandbox. It can't disrupt other -applications, except by explicitly declaring the permissions it needs -for additional capabilities not provided by the basic sandbox. These -permissions it requests can be handled by the operating in various ways, -typically by automatically allowing or disallowing based on certificates or -by prompting the user. The permissions required by an application are declared -statically in that application, so they can be known up-front at install time -and will not change after that.

- +

An application's process runs in a security sandbox. The sandbox is designed +to prevent applications from disrupting each other, except by explicitly +declaring the permissions they need for additional capabilities not +provided by the basic sandbox. The system handles requests for permissions +in various ways, typically by automatically allowing or disallowing based on +certificates or by prompting the user. The permissions required by an +application are declared statically in that application, so they can be known +up-front at install time and will not change after that.

Application Signing

-- cgit v1.1