Geoffrey Li

I changed `pub const USE_BATCH_ATTESTATION: bool = false;` to `pub const USE_BATCH_ATTESTATION: bool = true;` then I can use OpenSK to work with google account. It seems google account can...

Yes, I saw the contents, thank you @kaczmarczyck `Usually, the attestation private key is shared between a batch of at least 100,000 security keys of the same model. If you...

The certificate and private key shared here https://github.com/FeitianTech/OpenSK/releases are different with the materials inside OpenSK hardwares sold publicly. https://github.com/FeitianTech/OpenSK/releases was just regenerated to show how to use the GUI firmware...

AFAIK, it is impossible to do that unless you use a J-Link.

@bubundas17 , yes, the automatically generated certificate is not compliant with https://www.w3.org/TR/webauthn-1/#packed-attestation-cert-requirements , so Yubico demo server rejects it. I just changed `const USE_BATCH_ATTESTATION: bool = true` to try to...

1. I don't have dev board but only this USB dongle. 2. I used this USB dongle for a long time, I often downloaded latest OpenSK firmware to it. But...

Not work for me, after ``` 1. ./reset.sh 2. ./setup.sh 3. ./deploy.py --board=nrf52840_dongle_dfu --programmer=nordicdfu --no-app --dont-clear-apps (in bootloader mode) 4. ./deploy.py --board=nrf52840_dongle_dfu --opensk --programmer=nordicdfu (in bootloader mode) 5. ./tools/configure.py \...

I can not find any usb dfu way to erase code and data storage to have only MBR/bootloader left, tools from Nordic can not do either. If I can do...

`./deploy.py --board=nrf52840_dongle_dfu --erase_storage --programmer=nordicdfu ` is only available in `develop`, this `--erase_storage` option is introduced in https://github.com/google/OpenSK/pull/247 . If this option is very helpful, please add it to `stable` too.

After correct Line 9 of `boards/nordic/nrf52840_dongle_dfu/Cargo.toml` according to https://github.com/google/OpenSK/pull/351 , our nrf52840 USB dongle can work with develop source code. But on stable branch, it still reports 0xF2 when programming...