Use SHA256 to hash salted creator bytes for transaction ID #502
Conversation
This file contains 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
Code previously used whichever hash function the client supplied when connecting the Gateway. For some implementations this hash function may use a different algorithm or even just pass through bytes unchanged. Fabric requires that the salted creator bytes be SHA256 hashed when generating a transaction ID. Any other algorithm would cause an invalid transaction ID to be generated. Signed-off-by: Mark S. Lewis <mark_lewis@uk.ibm.com>
andrew-coleman
approved these changes
Nov 2, 2022
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.
Code previously used whichever hash function the client supplied when connecting the Gateway. For some implementations this hash function may use a different algorithm or even just pass through bytes unchanged. Fabric requires that the salted creator bytes be SHA256 hashed when generating a transaction ID. Any other algorithm would cause an invalid transaction ID to be generated.