Xamarin visual studio 2015 sha1签名 [英] Xamarin visual studio 2015 sha1 signature

查看:162
本文介绍了Xamarin visual studio 2015 sha1签名的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我刚刚更改了我的问题以添加更多步骤。希望这有助于理解我的问题。



APK最初是使用Xamarin Studio for Windows创建的(早在2016年初)。

我然后接管并使用Visual Studio创建一个APK包。



密钥库尚未提供给我,所以我不得不从当前的APK包中提取。来自.rsa文件的.Keystore文件使用来自java的keytool包含在APK中。

一旦完成,我就能获得别名,我也获得了.keystore密码。



我在Visual Studio中有存档版本构建我的代码,使用ad hoc发布我导入.keystore文件并使用正确的别名和密码发布,但是结果沙不一样。



有些东西我做得不正确或是VS没有正确使用导入的.keystore。



有没有办法,使用命令行工具辞职和APK fr一个.keystore文件



谢谢



我尝试过:



从visual studio创建一个包

Hi, i just changed my question to add more step. hope this help to understand my problem.

The APK was originally created using Xamarin Studio for windows (back in early 2016).
I then take over and now using Visual studio to create an APK package.

The keystore has not been provided to me, so i had to extract from the current APK package the .Keystore file from the .rsa file contained into the APK using keytool from java.
once this done i have been able to get the alias and i have also been provided the .keystore password.

I have the "archive" in visual studio in release build my code, using ad hoc publishing i have imported the .keystore file and published with the correct alias and password, but the resulting sha are not the same.

is there somethign i have done not correctly or is it that VS does not used properly the .keystore imported.

is there a way, using command line tool to "resign" and APK from a .keystore file

Thank's

What I have tried:

create a package from visual studio

推荐答案

获得相同SHA-1签名的唯一方法是有相同的内容:这是使用SHA-1哈希值的整个想法。如果它们不同,那么内容是不同的,可能无效 - 这就是整个想法。

如果你有不同的哈希值,那么它可能像原始内容一样简单,包括构建时间APK中的日期,日期或版本代码 - 任何更改,无论多么微不足道都会生成不同的SHA-1值。
The only way to get an identical SHA-1 signature is to have identical contents: that's the whole idea of using an SHA-1 hash value. If they are different, then the content is different, and probably not valid - that is the whole idea.
If you have a different hash, then it may be as simple as the original including a build time, date, or version code in the APK - any change, no matter how trivial will generate a different SHA-1 value.


这篇关于Xamarin visual studio 2015 sha1签名的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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