JDK 7的变化密钥工具输出 [英] JDK 7 changes keytool output

查看:216
本文介绍了JDK 7的变化密钥工具输出的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用的JDK keytool生成的谷歌地图API密钥指纹。虽然被拒绝了几次,我才意识到,我已经升级JDK 1.7最近。所以,我转我的目录到JDK6(感谢上帝,老版本依然存在。),并重复同样的命令:

I'm using keytool of JDK to generate the Google Maps API key fingerprint. While being rejected for several times, I realized that I've upgraded JDK to 1.7 recently. So I switch my dir to JDK6 (Thank god, the old version remains.), and repeated the same command:

D:\.android>"C:\Program Files\Java\jre6\bin\keytool" -list -alias androiddebugkey -keystore debug.keystore -storepass android -keypass android

和砰!有用。原来,这JDK7中产生的SHA1指纹而非MD5,这导致我​​提交给谷歌的拒绝。 所以,我不知道为什么发生这种情况的JDK的新版本。任何一个有一些线索?

and Bang! It works. Turned out that JDK7 generated the SHA1 fingerprint instead of MD5, which leads to the rejection of my submission to Google. So I'm wondering why this happens for the new version of JDK. Any one have some clues?

推荐答案

密钥工具命令的参数 -keyalg 这需要一个算法的名称,并根据该算法生成的关键。据我了解,那只是意味着默认算法该命令改变了。

The keytool command has the parameter -keyalg that takes an algorithm name and generates the key according to that algorithm. As far as I understand, it just means that the default algorithm for that command has changed.

我不知道是否是有意识的选择或错误 - 你可能需要将其报告给甲骨文

I do not know whether it is a conscious choice or a bug - you may want to report it to Oracle.

这篇关于JDK 7的变化密钥工具输出的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆