Android modified debug KeyStore file to make it consistent with formal keystore SHA1

Transferred from: http://blog.k-res.net/archives/1671.html

Android app development access to a variety of SDKs will find that there are many SDKs need to rely on the package name and KeyStore fingerprint hash to identify (Baidu Map SDK, Facebook SDK and so on ...) ), so that if you use the default auto-generated debug KeyStore, youwill 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 a conforming debug KeyStore, and then select the custom Debug KeyStore in the ADT settings of Eclipse.

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

Android modified debug KeyStore file to make it consistent with formal keystore SHA1