Upgrade the HMAC Relay to protect Raptoreum SmartNodes Smart Contracts#14
Open
Gapcoin1 wants to merge 1 commit into
Open
Upgrade the HMAC Relay to protect Raptoreum SmartNodes Smart Contracts#14Gapcoin1 wants to merge 1 commit into
Gapcoin1 wants to merge 1 commit into
Conversation
Upgrading the HMAC keys to 512 Bits from 128 Bits will provide security to protect the non-tampered flow of Smart Contracts and Assets through SmartNodes Making Man-In-The-Middle attacks to tamper much more difficult! However, I am not sure since SipaHash if the Bitcoin code even calls this function but only the HMACSha512.h
|
how does this work with the Future contracts under test... dev commits has dried up with the rise in the RTM price? |
Collaborator
|
Futures are the the protocol level not contract level. As to commits check the right branch and requests. |
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
3 participants
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.
Upgrading the HMAC keys to 512 Bits from 128 Bits will provide security to protect the non-tampered flow of Smart Contracts and Assets through SmartNodes
Making Man-In-The-Middle attacks to tamper much more difficult!
However, I am not sure since SipaHash if the Bitcoin code even calls this function but only the HMACSha512.h