Is it still the “norm” when it concerns less than 20% of the people that make up society? They didn’t say cars shouldn’t exist at all, just that they shouldn’t be the norm.
Not to mention they wrote “busses, trains” before talking about something exclusive to cities.
I’m another gnu pass user, made a similar complaint in one of the other threads. I see dessalines claiming here that they use passkeys just fine with a 'FOSS" password manager. I guess that means it’s up to us to contribute an implementation of some kind.
There’s a discussion/issue on the codeberg hosting of the passff extension that seems to lay out what is needed: https://codeberg.org/PassFF/passff/issues/581
EDIT: seems like it’s both simpler and more complex than I thought to achieve what I want. https://codeberg.org/PassFF/passff/issues/581 suggests it is “just” a local tweak. At the same time, any search I make for finding an actual implementation guide for authenticators is buried under pages of results for using passkeys in your own web app. The ecosystem’s current state seems to be “don’t bother, just trust us!”. Even the damn “passkeys.com” site is a barely disguised ad for OwnID.
I dunno, the browser could open a file picker and let me point it towards the passkey, or perhaps let me paste the key contents into a field?
It’s been several months since I looked into it, so maybe things have changed since, but I don’t see why the browser has to be hooked up to my password manager through a mechanism that seemingly can’t be user-piloted nor user-intercepted. How does a browser API require some external third-party software to be installed and configured to work?! It’s a public/private key pair at the end of the day, right? Not some novel algorithm, protocol, or whatever. Why can’t I simply tell the browser “here is where my existing passkeys reside; place any newly generated ones here as well”? Or perhaps “here is the program to call and here are the arguments to supply when you need to create and/or retrieve a given passkey”?
I don’t think I have claimed the standard itself is locking anyone out - let me correct that if I did. I have just not found a way to not be locked out of the feature itself in the products of big players like Google - my Google account(s) being the one service where I feel like I could actually benefit from using passkeys over passwords (not to mention one of those I have seen pushing the “replace all your passwords with passkeys!” messaging).
To be specific, my password manager is http://passwordstore.org/, (“the standard Unix password manager”).
Personal anecdote to illustrate: the last time I tried creating and using passkeys for my Google account, I got the impression they (Google) would only accept keys coming from either Google Authenticator (their 2fa smartphone app) or something like macos’s built-in keychain. No way to give them a key generated using a local, offline service that I could store however I want - it needed to be accessible using, basically, a big corpo['s software] as the intermediary. This coming from how their website would request the keys from my browser (which means mozilla seem to be in on it as well :/).
Given that I currently use a pure file-based password manager that I can move around and switch the keys for as I please, the current state of passkeys feels like a step back in terms of allowing me to control my digital identities.
Maybe it’s just from having not grown up in such a society, but I would find it infuriating to discuss things in such a roundabout way. How can you ever establish a common understanding when everything “sensitive” is hiding behind several layers of indirection ?