Skip to content

Conversation

@lovesh
Copy link
Contributor

@lovesh lovesh commented Jun 6, 2018

Minor change

lovesh added 3 commits April 2, 2018 20:44
Signed-off-by: Lovesh Harchandani <lovesh.bond@gmail.com>
Signed-off-by: Lovesh Harchandani <lovesh.bond@gmail.com>
Signed-off-by: Lovesh Harchandani <lovesh.bond@gmail.com>

The recipients decrypt the Authcrypt Meta messages and verify it like any other Authcrypt message. Then it hashes Elemental and verifies it matches the hash in the Meta. Then it decrypts Elemental using the key in Meta.
The recipients decrypt the Authcrypt Meta messages and verify it like any other Authcrypt message. Then it hashes Elemental and verifies it matches the hash `msg_hash` in the Meta.
If the `msg_hash` does not match the hash of the Elemental then it knows that either the sender did not calculate the hash correctly or the Cloud agent tampered the data.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a hash of the encrypted data seems like a homegrown approach to a MAC. Consider doing a MAC

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants