rust-u2f VS Coze

This project aims to support U2F / FIDO2 using fingerprint reader on Linux (via libfprint). The goal is to have the same user experience with 2FA using Windows Hello.

This project is based on https://github.com/danstiner/rust-u2f with minor modification (see my fork: https://github.com/ngxson/rust-u2f-pkexec)

Link to the project: https://github.com/ngxson/softu2f-fprintd-docker

I've considered adding FIDO2 support to the software-only U2F token I wrote ( https://github.com/danstiner/rust-u2f). It's a fair bit of work though, and I am not sure how comfortable I am with passwordless login unless the keys are kept purely in hardware such as a TPM.

That said, my reading of this post is that FIDO2 support will get built into Chromium directly, which is itself open source. Or if you do want a hardware key but running open software, I'd definitely recommend https://solokeys.com/, I've been following them for a long time.

Also there was some related discussion on this same article last week: https://news.ycombinator.com/item?id=31274677

On a Workspace account you only need U2F token emulator (https://github.com/danstiner/rust-u2f woks fine) and thenn you can setup u2f first and add normal TOTP in second step. But u2f must stay there. I don't have a personal account to try if it works the same.

As it becomes easier to emulate hardware tokens[1], Google may start limiting which ones it accepts. I believe they can use attestation keys to do that.

This is just a softer layer of security to slow down less sophisticated mass signup attempts.

They may very well eventually phase out TOTP, under the justification that it is not as secure, but I would be shocked if they ever retire the highly insecure SMS verification.

TOTP is really easy to implement, and adds a ton of value. I have a oneliner that takes a screenshot, extracts the QR code with zbarimg, and adds it to my pass[2] password database, which then hooks back into my browser. I use it whenever it is available because it is so low effort.

[1]: https://github.com/danstiner/rust-u2f

GitHub has a couple of others listed, but I have not tested them personally: Example https://github.com/danstiner/rust-u2f

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