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
Hi, The libfido2 have the C# wrapper for communicating FIDO over USB with FIDO2 and CTAP2 protocol.
So, When we are building this library on Windows OS following through ReadMe we are getting the error of "failed to build libressl" as shown below.
So, We tried with the releases(https://developers.yubico.com/libfido2/Releases/) for libfido2 library which is pre-build and with that we were able to communicate with the Fido device over USB and able to Reset device, change pin on device but when we execute the makecredential call we are getting below issue with the release library.
And with the release libraries of libfido2 why its showing the static path for cbor_isa_map(item),
file C:\Users\marte\libfido2\build\libcbor-0.8.0\src\cbor\maps.c, line 114
The text was updated successfully, but these errors were encountered:
I am also working on the same library. But stuck on reading the yubi keys. Can you please tell me how did you read the devices? How did you find the device path?
For me I can only open windows hello but not my Yubi key.
Hi, The libfido2 have the C# wrapper for communicating FIDO over USB with FIDO2 and CTAP2 protocol.
So, When we are building this library on Windows OS following through ReadMe we are getting the error of "failed to build libressl" as shown below.
So, We tried with the releases(https://developers.yubico.com/libfido2/Releases/) for libfido2 library which is pre-build and with that we were able to communicate with the Fido device over USB and able to Reset device, change pin on device but when we execute the makecredential call we are getting below issue with the release library.
And with the release libraries of libfido2 why its showing the static path for cbor_isa_map(item),
file C:\Users\marte\libfido2\build\libcbor-0.8.0\src\cbor\maps.c, line 114
The text was updated successfully, but these errors were encountered: