Use public key from AIK cert for signature algorithm initalization #29
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.
Details
Attempts to fix #28.
Validation of the TPM attestation for Windows Hello with TPM v2 is failing as the AIK certificate public key was an RSA key and the public key
pubArea
was an ECC key – which causes the gem to try to initialize anOpenSSL::SignatureAlgorithm::RSA
object with ancurve
keyword argument resulting in aunknown keyword
error.The problem is that we are using the key in the
pubArea
to verify the signature overcertInfo
whereas the WebAuthn spec states that: