2 ms·
Users can’t manage them and nobody has come up with software that can. I have worked with PhDs who can’t even manage ssh keys.
by SoftTalker 2y ago
Users can’t manage them and nobody has come up with software that can.
I have worked with PhDs who can’t even manage ssh keys.
- notpushkin 2y agoTooling problem, as always.
- thayne 2y agoIf only there was a standard protocol for trading credentials and a CSR or equivalent for a signed certificate. Kind of like ACME for client certs that uses login credentials instead of dns. And maybe then browser support for logging in using that to create a client cert instead of setting a cookie.
- et1337 2y agoIn case anyone misses the joke, I think this is what passkeys are.
- nirui 2y ago> PhDs who can’t even Not a good point. I've experienced PhDs who can't (even, some may add) write shell script. Maybe they just hate the syntax, or specifically the $ symbol, maybe both. But, they did do fine job otherwise and has successfully replaced me, a person who can write a bit shell script :(
- SoftTalker 1y agoThe point is that even very smart people in technical fields can just be bad at/not care/willfully refuse to use stuff like this. It's a non-starter for a general-purpose authentication mechanism if the user has to understand concepts such as "private" and "publc" keys. Even 2FA solutions like Google Authenticator are simple enough that you just need to scan a QR code but very few people use them and even fewer actually bother to print/save the backup emergency codes for use if they lose access to their auth device. People can (sometimes) handle passwords, and an emailed reset link if they forget.