certutil: Adding support for ed25519 public keys#9703
Merged
Conversation
kalafut
approved these changes
Aug 10, 2020
calvn
pushed a commit
that referenced
this pull request
Aug 17, 2020
calvn
added a commit
that referenced
this pull request
Aug 17, 2020
anwittin
pushed a commit
that referenced
this pull request
Sep 29, 2025
…) (#9712) * actions(install-tools): include os and arch in cache key When caching and/or restoring our tools we should include the os and arch in the key to ensure that we don't accidentally download the wrong tools on different runners. We also update the nightlies to specifically cache arm64 before running the tests. * actionlint: add arm self-hosted runner keys Signed-off-by: Ryan Cragun <me@ryan.ec> Co-authored-by: Ryan Cragun <me@ryan.ec>
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
2 participants
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 allows for supporting EdDSA (ed25519) static keys in the JWT backend.