-
Notifications
You must be signed in to change notification settings - Fork 121
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
Remove ENABLE_DILITHIUM flag #2082
Open
jakemas
wants to merge
17
commits into
aws:main
Choose a base branch
from
jakemas:mldsa-flag
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
5084da9
header collisions
jakemas f420d8f
ml_dsa unique constant names
jakemas a3fd830
rename duplicate functions
jakemas 4a7a61a
rename dilithium constants
jakemas 363d631
change generic names to mldsa specific
jakemas 2bbdfc9
added prefix for all mldsa functions to prevent conflicts
jakemas ae01f07
Merge branch 'main' into ml-dsa-unique-names
jakemas f96096f
unique names for poly
jakemas 436dde3
consistency in naming
jakemas 88d6602
renamed signature to sign
jakemas 03dcaf5
remove enable_dilithium flag
jakemas ed3b2d0
Merge branch 'main' into mldsa-flag
justsmth a304717
Merge branch 'main' into mldsa-flag
justsmth 32a57bb
Merge branch 'main' into mldsa-flag
jakemas 2261a5a
clean up comment double brace
jakemas 94d60d7
Merge branch 'mldsa-flag' of github.com:jakemas/aws-lc into mldsa-flag
jakemas 3c9fde8
removed unused dilithium pem string
jakemas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -576,7 +576,6 @@ w1AH9efZBw== | |
-----END CERTIFICATE----- | ||
)"; | ||
|
||
#ifdef ENABLE_DILITHIUM | ||
// This certificate is the example certificate provided in section 3 of | ||
//https://datatracker.ietf.org/doc/draft-ietf-lamps-dilithium-certificates/ | ||
static const char kMLDSA65Cert[] = R"( | ||
|
@@ -946,8 +945,6 @@ DhQcIi8= | |
-----END CERTIFICATE----- | ||
)"; | ||
|
||
#endif | ||
|
||
// kSANTypesLeaf is a leaf certificate (signed by |kSANTypesRoot|) which | ||
// contains SANS for example.com, [email protected], 127.0.0.1, and | ||
// https://example.com/. (The latter is useless for now since crypto/x509 | ||
|
@@ -2923,8 +2920,6 @@ TEST(X509Test, Ed25519Sign) { | |
ASSERT_TRUE(SignatureRoundTrips(md_ctx.get(), pub.get())); | ||
} | ||
|
||
#ifdef ENABLE_DILITHIUM | ||
|
||
TEST(X509Test, MLDSA65SignVerifyCert) { | ||
// This test generates a MLDSA65 keypair, generates and signs a | ||
// certificate, then verifies the certificate's signature. | ||
|
@@ -2995,8 +2990,6 @@ TEST(X509Test, TestBadParamsMLDSA65) { | |
ERR_clear_error(); | ||
} | ||
|
||
#endif | ||
|
||
static bool PEMToDER(bssl::UniquePtr<uint8_t> *out, size_t *out_len, | ||
const char *pem) { | ||
bssl::UniquePtr<BIO> bio(BIO_new_mem_buf(pem, strlen(pem))); | ||
|
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functions not actually marked as experimental/deprecated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the right mechanism for this?
OPENSSL_DEPRECATED
? Or should we create a similar macroOPENSSL_EXPERIMENTAL
(out of scope of this PR)?