Lines Matching full:applications
1 page.title=Signing Your Applications
39 <li><a href="{@docRoot}tools/publishing/versioning.html">Versioning Your Applications</a></li>
46 <p>The Android system requires that all installed applications be digitally signed with a
49 relationships between applications. The certificate is not used to control which applications the
51 perfectly allowable, and typical, for Android applications to use self-signed certificates.</p>
53 <p>The important points to understand about signing Android applications are:</p>
56 <li>All applications <em>must</em> be signed. The system will not install an application
63 <li>You can use self-signed certificates to sign your applications. No certificate authority is
111 applications. </p>
114 all of your applications with the same certificate, throughout the expected
115 lifespan of your applications. There are several reasons why you should do so: </p>
129 <li>Application modularity – The Android system allows applications that
131 applications so requests, so that the system treats them as a single application.
138 certificate. By signing multiple applications with the same certificate and
139 using signature-based permissions checks, your applications can share code and
146 applications.</p>
155 <li>If you will sign multiple distinct applications with the same key,
157 lifespan of <em>all versions of all of the applications</em>, including
158 dependent applications that may be added to the suite in the future. </li>
163 to ensure that users can seamlessly upgrade applications when
168 use a <a href="#cert">suitable certificate</a> to sign your applications. </p>
601 permission, that person could sign and distribute applications that maliciously
602 replace your authentic applications or corrupt them. Such a person could also
603 sign and distribute applications under your identity that attack other
604 applications or the system itself, or corrupt or steal user data. </p>
620 <li>Similarly, when signing your applications with Jarsigner,
