Open
Conversation
sign cert hash expected to be provided by HeliBoard developer
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Provides a way to verify obtained checking signing cert hash. Signing cert hash does not provided in that PR, HeliBoard developer needs to provide it on their own.
How to obtain signing cert hash? Simple: using
keytoolcommand line tool:keytool -list -v -keystore path/to/keystore.jks(you will be asked to provide password)keytool usually comes with JDK, in JDK bin folder, see http://stackoverflow.com/questions/5488339/how-can-i-find-and-run-the-keytool
Again, please provide signing key hash on your own using
keytooland modifying this PR.Closes #1852