Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message challenge should use hashing API #4333

Closed
AaronFeickert opened this issue Jul 21, 2022 · 0 comments
Closed

Message challenge should use hashing API #4333

AaronFeickert opened this issue Jul 21, 2022 · 0 comments
Assignees
Labels
A-security Area - Security related

Comments

@AaronFeickert
Copy link
Collaborator

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.

aviator-app bot pushed a commit that referenced this issue Jul 28, 2022
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.
@hansieodendaal hansieodendaal added the A-security Area - Security related label Aug 15, 2022
@jorgeantonio21 jorgeantonio21 self-assigned this Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-security Area - Security related
Projects
Archived in project
Development

No branches or pull requests

3 participants