You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Message challenges should use the new hashing API.
Additionally, the nomenclature for this is confusing. First, the hash output is used as the input message for the message "origin MAC", which is actually a signature. Additionally, it is not really a challenge, but simply a binding representation of certain message data and metadata. It may be useful to rename this in a way that makes its intent and design more obvious.
The text was updated successfully, but these errors were encountered:
Description
--- Fix issues #4138, #4333 and #4170.
Motivation and Context
--- Add domain separation and cipher authentication for out bound messaging
How Has This Been Tested?
--- Unit tests.
Message challenges should use the new hashing API.
Additionally, the nomenclature for this is confusing. First, the hash output is used as the input message for the message "origin MAC", which is actually a signature. Additionally, it is not really a challenge, but simply a binding representation of certain message data and metadata. It may be useful to rename this in a way that makes its intent and design more obvious.
The text was updated successfully, but these errors were encountered: