WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

1.4K

Archive: https://archive.today/r7752

From the post:

>Update: After reading more of the spec authors’ comments on open-source Passkey implementations, I cannot support this tech. In addition to what I covered at the bottom of this blog post, I found more instances where the spec authors have expressed positions that are incompatible with open-source software and user freedom:

Archive: https://archive.today/r7752 From the post: >>Update: After reading more of the spec authors’ comments on open-source Passkey implementations, I cannot support this tech. In addition to what I covered at the bottom of this blog post, I found more instances where the spec authors have expressed positions that are incompatible with open-source software and user freedom:

(post is archived)

[–] 1 pt 3mo

Same here. That’s what I’m using right now. KeepassXC can store one time password codes, which gives you control. Having a phone app store them is daft. Having an online service like Google store them is even more daft.

If you want more security you can have a Yubikey store the secret data and use their one time password app (runs on all major OSs) to generate the codes.

The one time password code standard allows you to keep your secret codes in non secure ways, and it lets you keep them in highly secure ways (like a dedicated one time password device). It’s up to you. No one thinks one time passwords are non secure just because you’re allowed to use them in non secure ways.