Extract out GLev encryption into its own operations #382
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rickwebiii
reviewed
Nov 20, 2024
rickwebiii
reviewed
Nov 20, 2024
rickwebiii
approved these changes
Nov 20, 2024
ryanorendorff
force-pushed
the
glev-encryption
branch
from
c1e2daf to
7a36a0d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Extracts out GLev encryptions into their own operations, and then uses these operations when performing GGSW operations.
This PR also changes the GGSW encryption of a scalar to convert it to a polynomial message first and then perform the encryption. This will slightly increase the encryption time for a GGSW ciphertext from a plaintext message, but reduces sources of bugs by only having one encryption method for GGSW.