Skip to content

Changes to SHAKE in preparation for Dilithium support #86

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

Merged
merged 1 commit into from
Feb 13, 2020

Conversation

bwesterb
Copy link
Member

  1. (Re)add support for SHAKE-256.
  2. Reduce allocations. The byte-slice in the shake State struct
    confused Go's escape analysis and forced it onto the Heap.
  3. Move out of dh/sidh as it will be used by sign/dilithium.

1. (Re)add support for SHAKE-256.
2. Reduce allocations.  The byte-slice in the shake State struct
   confused Go's escape analysis and forced it onto the Heap.
3. Move out of dh/sidh as it will be used by sign/dilithium.
Copy link
Contributor

@armfazh armfazh left a comment

Choose a reason for hiding this comment

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

Agree on moving shake package.
I think it is valuable to have your changes on shake internals in the go upstream version.

@bwesterb bwesterb merged commit 079bd20 into cloudflare:master Feb 13, 2020
@bwesterb
Copy link
Member Author

Ok, will prepare a PR later this week.

@bwesterb bwesterb deleted the move-shake branch February 13, 2020 11:05
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