Update sk-usbhid.c #767
Closed
Update sk-usbhid.c #767
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
Fix usage of windows://hello security key returning no attestation data.
|
Thanks for fixing this! Since the upstream PR has been merged, to prevent any unnecessary merge conflicts, we will get this change when we pull from upstream. |
ghost
mentioned this pull request
3 tasks
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.
Using libfido2 with windows://hello results in security key returning no attestation data. This currently fails due to fido_cred_verify_self failing.
According to Yubico/libfido2#840 this is not a bug in libfido2, but openssh instead has to skip the verify call if no attestation is given.
This fixes the issue by skipping attestation verification during key generation if there is no attestation.
Fixes PowerShell/Win32-OpenSSH#2040 and PowerShell/Win32-OpenSSH#2279
Upstreamed in openssh#542, but as this is a windows specific issue, maybe it can be fixed in the PowerShell build faster.