Define keystore signature calculation algorithm

[pecet66]

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Expected/desired behavior

Please provide exact Android keystore signature generation command in docs.

keytool -exportcert -alias [aliasname] -keystore [your app keystore path] | openssl sha1 -binary | openssl base64

Please confirm, if above command is correct.
Specifically, should base64 be generated from binary form of sha1?

---

Thanks! We'll be in touch soon.

[ljunquera]

I get this warning message:

The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /Users/xxxxxx/OneDrive/Personal/Development/Keystore/Android/keystore.jks -destkeystore /Users/xxxxxx/OneDrive/Personal/Development/Keystore/Android/keystore.jks -deststoretype pkcs12

[pecet66]

I just found out that MS made good utility to get this signature hash.
https://github.com/AzureAD/microsoft-authentication-library-for-android/tree/dev/package-inspector
It seems to work by displaying a list of installed packages and shows the signature hash for each package.

It is the easiest way to get this signature hash I found so far.