Modify the password of the Android signing certificate KeyStore, aliases alias, and alias password

Command line Build KeyStore

DOS access to the JDK Bin directory

Run the following command:

Keytool-genkey-alias android.keystore-keyalg rsa-validity 20000-keystore android.keystore

(-validity 20000 represents the number of days of validity), and when the command is completed, the Android.keystore is generated in the bin directory

View command Keytool-list-keystore "Android.keystore" Enter the KeyStore password you set

Before testing the custom debug keystore for Eclipse ADT, I sent a blog post about the specifications of the debug certificate: The Custom debug keystore for Eclipse ADT, the required certificate specification, There are rules for passwords and alias names for custom debug certificates and for alias passwords. In fact, Android application development access to a variety of SDKs will find that there are many SDK is required by the package name and KeyStore fingerprint hash to identify (Baidu Map SDK, Facebook SDK, etc...) ), so that if you use the default auto-generated debug KeyStore, you will have some trouble with debugging your development. At this time can be modified by the official release KeyStore, to generate a "obey the rules" of the temporary custom debugging certificate for development use, it is more convenient, the specific method is as follows:

1. First of all, of course, first copy a formal certificate as the temporary debug certificate to be modified.

2. Modify the command for the KeyStore password (keytool is the command-line tool for the JDK):

Keytool-storepasswd-keystore My.keystore

Where My.keystore is a copy of the certificate file, you will be prompted to enter the certificate's current password, and the new password and repeat the new password confirmation. This step requires changing the password to Android.

3. Modify the alias of KeyStore:

Keytool-changealias-keystore my.keystore-alias my_name-destalias androiddebugkey

In this step, My_name is the certificate in the current Alias,-destalias specified is to be modified to the alias, here according to the rules, instead of androiddebugkey! This command will prompt you to enter the KeyStore password and the current alias password.

4. Modify Alias's password:

Keytool-keypasswd-keystore My.keystore-alias Androiddebugkey

After this step, you will be prompted to enter the KeyStore password, alias password, and then prompt for a new alias password, similarly, according to the rules, change to android!

After the execution of the above several operations, My.keystore is the rules of the debug KeyStore, and then in Eclipse's ADT settings to select the custom debug KeyStore, as follows:

You can also see the MD5 of the certificate and the SHA1 fingerprint.

PS: The above 3-step command line has no sequencing.

However, one of the problems is that the original mobile phone installed the app, when the password changed, then export, and then install, the hand of the opportunity to suggest that there is a signature conflict application,
This seems to have to uninstall the original app, and then reinstall the new one.

This modification will also change the fingerprint hash and will be judged as a signature conflict.

Modify the password of the Android signing certificate KeyStore, aliases alias, and alias password