Coze VS keepassxc

https://cyphr.me/coze#?input={%22pay%22:{%22msg%22:%22Hello,...

We're working on an open source alternative to Passkeys starting with Coze https://github.com/Cyphrme/Coze.

We have not yet published our next steps, but we will soon.

You can play with Coze here using the online tool. There is also the simple tool.

Base64 also has problems, in particular with canonicalization. This is a problem that I think needs more awareness in the industry. It does seem to recently gained some awareness (See the paper, "Base64 Malleability in Practice")

Coze is a cryptographic JSON messaging specification designed for human readability.

Our website is already using public key authentication using Coze. https://github.com/Cyphrme/Coze. We've been doing public key authentication for around 2 years now. No passwords needed, just public key auth.

On my website, I'm doing authentication via simple public key authentication using Coze.

No passwords. No email. No Google. https://github.com/Cyphrme/Coze

KeepassXC supports exporting, but i don't think it is released in a stable version / to the public yet:

https://github.com/keepassxreboot/keepassxc/pull/8825

If you use KeePass, make sure you use the KeePassXC variant. KeePass is dead.

https://keepassxc.org/

That's why you use the superior one, KeePassXC, as linked in the NIST link: https://github.com/keepassxreboot/keepassxc/discussions/9433

Over there, they got pissed about people constantly bugging them about it and closed the bug with the last comment reading:

for the internet, use a password manager like keepassxc with a strong password.

Another regression is that KeePassX/C AutoType doesn't work with Wayland, so now instead of a simple CTRL+V in KeePassXC, I have to separately copy and paste the user and the pass.

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