The cauldron is already warm. I encourage people to read these issue trackers.

https://github.com/keepassxreboot/keepassxc/issues/10407#iss...

https://github.com/keepassxreboot/keepassxc/issues/10406

"The unfortunate piece is that your product choices can have both positive and negative impacts on the ecosystem as a whole. I've already heard rumblings that KeepassXC is likely to be featured in a few industry presentations that highlight security challenges with passkey providers, the need for functional and security certification, and the lack of identifying passkey provider attestation (which would allow RPs to block you, and something that I have previously rallied against but rethinking as of late because of these situations)."

"This implementation is not spec compliant and has the potential to be blocked by relying parties."

Proponents keep trying to hand wave away the attestation lock-in problem as some vague faraway threat that we may never encounter. It isn't. It's the actual plan.

Just make sure you trust the cauldron you choose.

[dead]