Add support for Ed25519 keys #156
Open
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
e-nomem
force-pushed
the
add-ed25519-keys
branch
from
ece3a2a to
d17275a
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.
This is basically the same as #26 but implements the automatic algo selection by checking the firmware version as you mentioned in the other PR.
Yubikeys officially added support for Ed25519 keys in firmware version 5.7.0. Upstream piv-go added support for it in go-piv/piv-go#157 (released in
v2.2.0).Note that Yubikey firmware 5.4.0 (technically 5.4.2 but I used the same version check as piv-go, see this comment) added support for AES management keys so I also used the same firmware version detection method to upgrade the management key to AES256.
Tested locally on macOS Sequoia with Yubikey firmware 5.7.1