Skip to content

Conversation

@iherman
Copy link
Member

@iherman iherman commented Nov 13, 2025

I read through the full document and, while reading, I hit some spelling errors or editorial issues. I propose some changes in this PR, I hope it will be helpful.

I had some more issues with the technical content, but I would leave them for the time when the document is ready for a more public review. I am happy to re-review the document at the time, just ping me...

A general issue: as an outsider, I would welcome, for each major section, a very short technical/mathematical summary of the underlying approach or approaches are, which would also shed some lights on the interrelationships of the sections. An example: I presume (but that is only a guess) that a MAC means combining the original message with the secret key (is it simply a concatenation?) and hash the result. If so, adding this information at the start of the section would be greatly helpful for the intended audience, imho.


Preview | Diff

I read through the full document and, while reading, I hit some spelling errors or editorial issues. I have put them into this PR, I hope it will be helpful.

I had some more issues with the technical content, but I would leave them for the time when the document is ready for a more public review. I am happy to re-review the document at the time, just ping me...
@iherman iherman requested a review from simoneonofri November 13, 2025 12:16
@Frosne
Copy link
Member

Frosne commented Nov 14, 2025

I read through the full document and, while reading, I hit some spelling errors or editorial issues. I propose some changes in this PR, I hope it will be helpful.

I had some more issues with the technical content, but I would leave them for the time when the document is ready for a more public review. I am happy to re-review the document at the time, just ping me...

A general issue: as an outsider, I would welcome, for each major section, a very short technical/mathematical summary of the underlying approach or approaches are, which would also shed some lights on the interrelationships of the sections. An example: I presume (but that is only a guess) that a MAC means combining the original message with the secret key (is it simply a concatenation?) and hash the result. If so, adding this information at the start of the section would be greatly helpful for the intended audience, imho.

Preview | Diff

You seem to fail CI..

To be honest, I have no idea how that character appeared in the output. Anyway... I have just removed it.
Copy link
Contributor

@simoneonofri simoneonofri left a comment

Choose a reason for hiding this comment

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

Thank you @iherman. Regarding the layers, maybe we can refer the Threat Stack differentiating the:

  • Cryptographic primitives
  • Mathematical foundations

@verocri verocri merged commit cc56fe8 into main Nov 25, 2025
1 check passed
github-actions bot added a commit that referenced this pull request Nov 25, 2025
SHA: cc56fe8
Reason: push, by verocri

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

5 participants