Searched full:application (Results 1 – 25 of 182) sorted by relevance
12345678
| /docs/source.android.com/src/security/overview/ |
| D | app-security.jd | 1 page.title=Application security
27 <p>Android provides an open source platform and application environment for mobile
33 <p>The main Android application building blocks are:</p>
39 receivers, and content providers described below) in an application. This also
46 Activities never display UIs. Typically, one of the application's Activities
47 is the entry point to an application.</p>
51 or in the context of another application's process. Other components "bind" to
60 …tent.html">Intent</a> is issued by the operating system or another application. An application may
66 <p>All applications on Android run in an Application Sandbox, described earlier in this document.
67 By default, an Android application can only access a limited range of system
[all …]
|
| D | kernel-security.jd | 30 native code is constrained by the Application Sandbox. Whether that code is
31 the result of included application behavior or an exploitation of an
32 application vulnerability, the system is designed to prevent the rogue
33 application from harming other applications, the Android system, or the device
64 <h2 id="the-application-sandbox">The Application Sandbox</h2>
66 means of identifying and isolating application resources. The Android system
67 assigns a unique user ID (UID) to each Android application and runs it as that user
71 <p>This sets up a kernel-level Application Sandbox. The kernel enforces security
75 limited access to the operating system. If application A tries to do something
76 malicious like read application B's data or dial the phone without permission
[all …]
|
| D | implement.jd | 58 application code using the Android SDK and correct any identified issues.</li>
90 <p>Application signatures play an important role in device security and are used
92 for signing applications, it is important to consider whether an application
103 keys. This often occurs when creating an application for different devices,
104 especially when using the platform key. If the application is
105 device-independent, use the same key across devices. If the application is
113 your application has a unique package name. Best practices:</p>
121 <li>Create an application package name that is clearly associated with your
163 application with low or no privileges to handle network traffic.</li>
185 <p>The Android Application Sandbox provides applications with an expectation of
[all …]
|
| D | updates-resources.jd | 64 defined by the type of application or process or the area in which it runs.
75 A process that is significantly more limited than a normal application.</td>
79 <td>A third-party application or process.<br />
81 An application or process that runs in the SELinux <code>untrusted_app</code> domain.</td>
85 <td>An application or process with capabilities that are restricted by SELinux
88 An application or process with important privileges that a third-party
89 application cannot obtain.</td>
145 <li> A general bypass for operating system protections that isolate application data
174 Safe Mode and removing the problematic application, or by a factory reset if
267 application that attempts to exploit a security bug. For applications installed
[all …]
|
| /docs/source.android.com/src/security/apksigning/ |
| D | index.jd | 1 page.title=Application Signing
28 Application signing allows developers to identify the author of the application
29 and to update their application without creating complicated interfaces and
30 permissions. Every application that is run on the Android platform must be <a
37 On Google Play, application signing bridges the trust Google has with the
38 developer and the trust the developer has with their application. Developers
39 know their application is provided, unmodified, to the Android device; and
40 developers can be held accountable for behavior of their application.
43 On Android, application signing is the first step to placing an application in
44 its Application Sandbox. The signed application certificate defines which user
[all …]
|
| /docs/source.android.com/src/security/ |
| D | index.jd | 37 value, the platform offers an application environment that protects the
61 application communications. Android security released a tool for testing SSL
72 into permissions requested by each application and control over those
94 browser or SMS application.
99 Android provides an open source platform and application environment for mobile
108 the Linux Kernel is restricted by the Application Sandbox.
128 <li><strong>Android Application Runtime</strong>: Android applications are most
133 the Application Sandbox. Applications get a dedicated part of the filesystem in
148 development environment that supports any third-party application. Google Play
170 application
[all …]
|
| /docs/source.android.com/src/devices/tech/datausage/ |
| D | kernel-overview.jd | 19 <p>The per-application/delegated data usage monitoring and tracking
30 restrict background data traffic for an application (refer to
36 per-socket basis for every application using the unique UID of the
37 owning application. There are two tag components associated with any
39 the application which is responsible for the data transfer (Linux
41 the UID of the calling application). The second tag component is used
42 to support additional characterization of the traffic into application
43 developer specified categories. Using these application level tags, an
44 application can profile the traffic into several sub-categories.</p>
48 to the UID of the requesting application using the
|
| /docs/source.android.com/src/security/bulletin/ |
| D | 2015-08-01.jd | 142 application into the wrong process</td>
172 application has already been installed, Verify Apps will notify the user and
207 <p>The affected functionality is provided as an application API and there are
241 <p>The affected functionality is provided as an application API and there are
276 <p>The affected functionality is provided as an application API and there are
312 <p>The affected functionality is provided as an application API and there are
349 <p>The affected functionality is provided as an application API and there are
385 <p>The affected functionality is provided as an application API and there are
420 <p>The affected functionality is provided as an application API and there are
455 <p>The affected functionality is provided as an application API and there are
[all …]
|
| D | 2016-10-01.jd | 434 when they attempt to install a detected rooting application—no matter where it
437 vulnerability. If such an application has already been installed, Verify Apps
438 will notify the user and attempt to remove the detected application.</li>
521 application to register arbitrary services that would normally be provided by a
555 local malicious application to clear the device PIN or password. This issue is
587 malicious application to execute arbitrary code within the context of a
590 third-party application.
639 application to execute arbitrary code within the context of a privileged
642 third-party application.
672 local malicious application to execute arbitrary code within the context of a
[all …]
|
| D | 2015-09-01.jd | 125 application has already been installed, Verify Apps will notify the user and
195 sockets could allow a malicious application to execute arbitrary code in
226 application to execute arbitrary code within the context of the another app’s
229 <p>This issue is rated as High severity because it allows a malicious application
230 to gain privileges not accessible to a third-party application.</p>
257 application to execute arbitrary code within the context of the keystore
262 not accessible to a third-party application.</p>
283 malicious message to a service, allow a malicious application to execute
287 not accessible to a third-party application.</p>
308 messages could enable a malicious application to send an SMS message that
[all …]
|
| D | 2015-10-01.jd | 167 application has already been installed, Verify Apps will notify the user and
423 <p>The affected functionality is provided as an application API and there are
488 <p>The affected functionality is provided as an application API and there are
519 leveraged by a malicious application when calling into the KeyStore APIs. This
520 application could cause memory corruption and arbitrary code execution in the
523 application.</p>
546 could allow a malicious application to execute arbitrary code within the
548 a malicious application to access privileges not accessible to a third-party
549 application.</p>
576 malicious application to execute arbitrary code within the context of an
[all …]
|
| D | 2016-04-02.jd | 42 by a rooting application. <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1805">CV…
238 such an application has already been installed, Verify Apps will notify the
517 malicious application to execute arbitrary code within the kernel. This issue
549 application to execute arbitrary code within the kernel. This issue is rated as
578 malicious application to execute arbitrary code within the context of the
608 local malicious application to execute arbitrary code in the kernel. This issue
645 enable a local malicious application to execute arbitrary code within the
646 context of an elevated system application. This issue is rated as High severity
650 permissions privileges, which are not accessible to a third-party application.</p>
680 permissions privileges, which are not accessible to a third-party application.</p>
[all …]
|
| D | 2016-12-01.jd | 391 when they attempt to install a detected rooting application—no matter where it
394 vulnerability. If such an application has already been installed, Verify Apps
395 will notify the user and attempt to remove the detected application.</li>
573 enable a local malicious application to execute arbitrary code within the
576 accessible to a third-party application.
611 application to use a specially crafted file to cause a device hang or reboot.
714 possibility of remote code execution in an application that uses the
788 local malicious application to access system functions beyond its access level.
824 malicious application to access system functions beyond its access level. This
859 application to execute arbitrary code within the context of a privileged
[all …]
|
| D | 2017-02-01.jd | 353 when they attempt to install a detected rooting application—no matter where it
356 vulnerability. If such an application has already been installed, Verify Apps
357 will notify the user and attempt to remove the detected application.</li>
556 remote code execution in an application that uses this library.
592 possibility of remote code execution in an application that uses this library.
661 local malicious application to execute arbitrary code within the context of a
664 to a third-party application.
717 malicious application to execute arbitrary code within the context of a
720 to a third-party application.
754 malicious application to execute arbitrary code within the context of a
[all …]
|
| D | 2016-05-01.jd | 273 application—no matter where it comes from. Additionally, Verify Apps attempts
275 a privilege escalation vulnerability. If such an application has already been
277 application.</li>
396 could enable a local malicious application to execute arbitrary code within the
432 could enable a secure local malicious application to execute arbitrary code
474 enable a local malicious application to execute arbitrary code within the
517 a local malicious application to execute arbitrary code within the context of
573 malicious application to execute arbitrary code within the context of the
610 local malicious application to execute arbitrary code within the context of the
644 could allow a local malicious application to access personal identifiable
[all …]
|
| /docs/source.android.com/src/devices/sensors/ |
| D | sensor-stack.jd | 38 <p>When registering to a sensor, the application specifies its preferred sampling
41 <li> For example, an application might register to the default accelerometer,
44 <li> The application will receive events from the accelerometer at a rate of at
50 framework level, only a single application could access each sensor at any
53 <li> When a first application registers to a sensor, the framework sends a request
56 into account requirements from each application and sends the updated requested
62 …um reporting latency</a> will be the minimum of the requested ones. If one application requests one
68 <li> When the last application registered to one sensor unregisters from it, the
76 <li> When an application requests a specific sampling frequency, there is no
77 guarantee that events won’t arrive at a faster rate. If another application
[all …]
|
| /docs/source.android.com/src/devices/tech/config/ |
| D | runtime_perms.jd | 27 <p>The Android 6.0 application permission model is designed to make permissions
41 accesses a specific feature), but must allow the user to grant/deny application
52 <p>Users can revoke application permissions using the Apps menu in Settings.</p>
69 isolated application-level features with minimal risk to other applications, the
71 automatically grants normal permissions to a requesting application at
81 process. Application software requirements include:</p>
85 <li>Apps must prompt users to grant application permissions at runtime. For
97 UID with another application that has the necessary permissions. For details,
108 <p>When integrating the Android 6.0 application runtime permissions model, you
140 <li>Share a UID with another application that has the necessary permissions. Use
[all …]
|
| /docs/source.android.com/src/compatibility/2.2/ |
| D | android-2.2-cdd.xhtml | 28 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
53 <a href="#section-5">5. Application Packaging Compatibility</a><br/>
82 <a href="#section-8.15">8.15. Application Shared Storage</a><br/>
149 <a name="resources13"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
179 web-application APIs. This section details the hard and soft APIs that are
186 Android applications. The Android application programming interface (API) is
199 be enforced at application compile time. This section details the "soft" APIs
228 accessible to third-party application code. For Android 2.2, this field MUST have
340 <a name="section-3.2.3.1"></a><h4>3.2.3.1. Core Application Intents</h4>
361 <li>LivePicker (that is, the Live Wallpaper picker application; MAY be omitted
[all …]
|
| /docs/source.android.com/src/compatibility/4.0/ |
| D | android-4.0-cdd.xhtml | 34 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
42 <a href="#section-3.3.1">3.3.1 Application Binary Interfaces</a><br/>
60 <a href="#section-3.8.7">3.8.7. Recent Application Display</a><br/>
67 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
85 <a href="#section-7.1.5">7.1.5. Legacy Application Compatibility Mode</a><br/>
127 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
201 <a name="resources20"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
256 Android applications. The Android application programming interface (API) is
274 be enforced at application compile time.</p>
301 accessible to third-party application code. For Android 4.0.1 - 4.0.2, this
[all …]
|
| /docs/source.android.com/src/compatibility/2.1/ |
| D | android-2.1-cdd.xhtml | 62 <a name="resources13"/><li>Application Resources: <a href="http://code.google.com/android/reference…
91 web-application APIs. This section details the hard and soft APIs that are
98 Android applications. The Android application programming interface (API) is
111 be enforced at application compile time. This section details the "soft" APIs
140 accessible to third-party application code. For Android 2.1, this field MUST have
252 <h4>3.2.3.1. Core Application Intents</h4>
273 <li>LivePicker (that is, the Live Wallpaper picker application; MAY be omitted
323 application .apk file as an ELF .so file compiled for the appropriate device
350 <p>Device implementations MUST accurately report the native Application Binary
386 Browser application. What's more, the standalone Browser MAY be based on an
[all …]
|
| /docs/source.android.com/src/compatibility/4.2/ |
| D | android-4.2-cdd.xhtml | 34 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
42 <a href="#section-3.3.1">3.3.1 Application Binary Interfaces</a><br/>
60 <a href="#section-3.8.7">3.8.7. Recent Application Display</a><br/>
70 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
93 <a href="#section-7.1.5">7.1.5. Legacy Application Compatibility Mode</a><br/>
137 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
213 <a name="resources20"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
270 <a name="resources77"></a><li>Android Application Development-Related Settings: <a href="http://dev…
284 Android applications. The Android application programming interface (API) is
302 be enforced at application compile time.</p>
[all …]
|
| /docs/source.android.com/src/compatibility/2.3/ |
| D | android-2.3-cdd.html | 27 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
51 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
107 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
184 <a name="resources18"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
222 web-application APIs. This section details the hard and soft APIs that are
229 Android applications. The Android application programming interface (API) is
246 be enforced at application compile time. This section details the "soft" APIs
275 accessible to third-party application code. For Android 2.3, this field MUST have
392 <a name="section-3.2.3.1"></a><h4>3.2.3.1. Core Application Intents</h4>
413 <!-- <li>LivePicker (that is, the Live Wallpaper picker application; MAY be omitted
[all …]
|
| D | android-2.3-cdd.xhtml | 28 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
52 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
108 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
185 <a name="resources18"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
223 web-application APIs. This section details the hard and soft APIs that are
230 Android applications. The Android application programming interface (API) is
247 be enforced at application compile time. This section details the "soft" APIs
276 accessible to third-party application code. For Android 2.3, this field MUST have
393 <a name="section-3.2.3.1"></a><h4>3.2.3.1. Core Application Intents</h4>
414 <!-- <li>LivePicker (that is, the Live Wallpaper picker application; MAY be omitted
[all …]
|
| /docs/source.android.com/src/compatibility/4.3/ |
| D | android-4.3-cdd.xhtml | 34 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
42 <a href="#section-3.3.1">3.3.1 Application Binary Interfaces</a><br/>
61 <a href="#section-3.8.8">3.8.8. Recent Application Display</a><br/>
70 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
93 <a href="#section-7.1.5">7.1.5. Legacy Application Compatibility Mode</a><br/>
139 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
215 <a name="resources20"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
272 <a name="resources77"></a><li>Android Application Development-Related Settings: <a href="http://dev…
289 Android applications. The Android application programming interface (API) is
307 be enforced at application compile time.</p>
[all …]
|
| /docs/source.android.com/src/devices/accessories/ |
| D | custom.jd | 53 (rather than the adb or audio protocol), you must provide an Android application
72 <li>When planning to build an Android application that communicates with your
74 <a href="http://developer.android.com/tools/adk/adk2.html#src-download">application
87 application that handles specialized communication such as data input or control
102 <li>When planning to build an Android application that communicates with your
104 <a href="http://developer.android.com/tools/adk/adk2.html#src-download">application
118 secondary software application is required on the Android device.</p>
|
12345678