David Sugar

 Thanks! Works perfectly :)

Thanks 👍 a refresh would be super helpful, otherwise the confirmation dialog doesn't pop up automatically.

Btw if you have questions/ want to know something specific don't hesitate to ask

 Looks pretty good! The dialog is now instantly shown.

The fido2 protocol involves 3 entities: the authenticator, a client (e.g. web browser) and a relying party (e.g. github authentication server). Ctap2 is the protocol that handles communication between authenticator...

I gonna make an additional QA entry 👍

Happy to help. A lot of people use webauthn, fido2 and passkey interchangeably which makes it pretty confusing.

It's absolutely ok, thanks!

Hi sorry for the late reply. For embedded projects you have to setup an allocator yourself. The easiest way you can do that is to use a fixed buffer allocator....

I switched to a custom database format https://r4gus.github.io/ccdb/ because there are a few things in kdbx that I dislike. Nevertheless, adding kdbx4 support is still a good idea.