Add ML-DSA support for TLSv1.3 (draft-tls-westerbaan-mldsa-00) #2020
Conversation
This file contains hidden or 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
|
Merged with changes; in particular ML-DSA is still disabled until we finish changes to prevent negotiation before TLS 1.3. I generated ML-DSA certificates for TLS testing a few months ago. They are available in the bc-test-data repository which would usually be setup side-by-side with bc-java (https://github.com/bcgit/bc-test-data/tree/main/tls/credentials). |
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.
This PR adds support for ML-DSA in TLSv1.3.
Validation and certificate testing are required, but currently, it's not possible to generate ML-DSA certificates using the released gnutls certtool. Therefore, these tests have not been included in this PR.
If you have any suggestions or alternatives for generating ML-DSA certificates, please let me know.