kaczmarczyck

Hi! Can you please specify what kind of support you request? If you want to run OpenSK on your hardware, the Nordic chip is supported. However, BLE is not yet...

We don't support new hardware on request. We do accept contributions, so if you find out how to install OpenSK on this platform, feel free to extend our documentation.

Works for me on a fresh MDK. Maybe you need to erase the persistent storage, and the blinking is a panic. In that case, follow the instructions above again, but...

Ah right, understood. Is this problem OpenSK related, because you can't enter DFU mode since you flashed an OpenSK, and it worked before?

In that case, I'll have to understand how to reproduce. Please let me know if you have any pointers etc. about that.

Thanks for helping! Do you know if the unresponsive bootloader was caused by OpenSK? @chimpnz

As indicated, I expected this to automatically checked. No strong opinion however, where are ASCII art examples that would need refactoring?

Just wanted to know if you have an intuition about how much we have to change. But it seems like our code would be nicer with correct length comments? But...

The current implementation in the `develop` branch follows [review draft 2 of CTAP 2.1](https://fidoalliance.org/specs/fido-v2.1-rd-20201208/fido-client-to-authenticator-protocol-v2.1-rd-20201208.html). PRs merged for finishing support: - #254 - #256 - #263 - #265 - #267 -...

Features around `alwaysUv`, enterprise attestation and PIN protocol V2 (PRs for the latter: #293, #295, #296) are implemented. Missing work: - remaining updates for existing command algorithms - missing changes...