Repository navigation
Conversation
When built with Go 1.27 or later with crypto/mldsa package.
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
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.
A less invasive variant of #517 using
crypto/mldsafrom Go 1.27.Of those two commits, I'm mostly interested in the end-entity one, as I need it for the client testing. I'd love to see the account key support as well, but it is blocked on go-jose/go-jose#272.
Don't know what's the proper convention for this kind of conditional compilation and will take suggestions. I do have a preference for keeping older Go toolchains supported, though, as I test on wide variety of sometimes outdated systems.