You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by vikinatora March 21, 2024
Hello, we're working on client facing JS library for interacting with NEAR blockchain. Currently, we have successfully implemented functionality that creates a key pair using fido2 and can recover the key pair using the ES256 signature from attestationResult. However, some Windows machines use RS256 algortihm for signing which breaks the logic.
My question whether our use case is possible to be fulfilled when the signature is made using RS256 algorihm? Please let me know if you need more info regarding anything.
Thanks in advance!🙏
The text was updated successfully, but these errors were encountered:
Discussed in #166
Originally posted by vikinatora March 21, 2024
Hello, we're working on client facing JS library for interacting with NEAR blockchain. Currently, we have successfully implemented functionality that creates a key pair using fido2 and can recover the key pair using the ES256 signature from
attestationResult
. However, some Windows machines use RS256 algortihm for signing which breaks the logic.This is the file with our main biometric logic: https://github.com/near/near-api-js/blob/master/packages/biometric-ed25519/src/index.ts.
My question whether our use case is possible to be fulfilled when the signature is made using RS256 algorihm? Please let me know if you need more info regarding anything.
Thanks in advance!🙏
The text was updated successfully, but these errors were encountered: