Robin Krahl

You will probably run into issues with repeated calls to `log::set_logger` if you also test applying the configuration.

> If an allowList is present and is non-empty, locate all denoted credentials present on this authenticator and bound to the specified rpId. https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html#authenticatorGetAssertion I think this means that we...

I’ve drafted a PR against the Nitrokey fork because it has fixed some formatting issues and uses a newer Trussed version: https://github.com/Nitrokey/fido-authenticator/pull/32. Please review there. I’ll backport it for the...

@spectras This issue should be fixed for the Nitrokey 3 with [v1.5.0-test.20231030](https://github.com/Nitrokey/nitrokey-3-firmware/releases/tag/v1.5.0-test.20231030).

AFAIS https://github.com/Nitrokey/heads/issues/48 is about the Nitrokey 3, but libnitrokey is only used with Nitrokey Pro or Storage. Can you add more details please?

The particular problem in this issue was caused by the fact that the Nitrokey Pro and Storage internally used the OpenPGP smartcard to implement the (H)OTP feature. As GnuPG caches...

Closing as this has been implemented as a custom backend for websmartcard, see: https://github.com/Nitrokey/nitrokey-websmartcard-rust/pull/16

Please rebase and drop the postcard update and revert commits.

Thanks! When updating our fork, I realized that updating blake2 breaks the HmacBlake2s mechanism. This will probably cause the CI to fail. It should be easy to fix by replacing...

I think we could further modularize this PR by moving the backends out of Trussed. The backend enum could be defined together with the platform by the runner. The backend...