Lines Matching full:keystore
99 private key you use are your own, you must provide the password for the keystore and key alias.</p>
190 a debug keystore and key. This debug key is then used to automatically sign the APK, so
193 <p>The SDK tools create the debug keystore/key with predetermined names/passwords:</p>
195 <li>Keystore name: "debug.keystore"</li>
196 <li>Keystore password: "android"</li>
202 <p>If necessary, you can change the location/name of the debug keystore/key or
203 supply a custom debug keystore/key to use. However, any custom debug
204 keystore/key must use the same keystore/key names and passwords as the default
228 compile your app, the build script generates a keystore/key and signs the APK for you.
249 <p>To fix this problem, simply delete the <code>debug.keystore</code> file.
255 <p>The next time you build, the build tools will regenerate a new keystore and debug key.</p>
277 generate a new keystore and private key in the process. So if you use Eclipse, you can
314 for both the keystore and key.</p>
316 <p class="warning"><strong>Warning:</strong> Keep the keystore file you generate with Keytool
366 <td><code>-keystore <keystore-name>.keystore</code></td><td>A name
367 for the keystore containing the private key.</td>
371 keystore.</p><p>As a security precaution, do not include this option in your
379 <pre>$ keytool -genkey -v -keystore my-release-key.keystore
383 passwords for the keystore and key, and to provide the Distinguished
384 Name fields for your key. It then generates the keystore as a file called
385 <code>my-release-key.keystore</code>. The keystore and key are
386 protected by the passwords you entered. The keystore contains
388 will use later, to refer to this keystore when signing your application. </p>
431 and aligning for you, if you have provided the path to your keystore and the name of
433 the build script will prompt you for your keystore and alias password when you perform
438 To learn how to specify your keystore and alias in the {@code ant.properties} file,
449 the keystore containing your private key is available.</p>
452 application's APK and the keystore containing the private key with which to
461 <td><code>-keystore <keystore-name>.keystore</code></td><td>The name of
462 the keystore containing your private key.</td>
477 keystore. </p><p>As a security precaution, do not include this option
492 <code>my_application.apk</code>, using the example keystore created above.
495 <pre>$ jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore
499 passwords for the keystore and key. It then modifies the APK
565 export a <em>signed</em> APK (and even create a new keystore,
585 (or creating a new keystore and private key).</p>
596 your keystore and passwords in an unsecured location such that a third-party
615 <li>Select strong passwords for the keystore and key.</li>
624 persons know your keystore and key passwords.</li>
625 <li>Keep the keystore file containing your private key that you <a href="#cert">generate with the
