Comment If security matters, why are browsers killing off (Score 1) 111
The problem we humans have with passwords is obvious. Back when a soldier had to remember a single word to pass a checkpoint, that was it - one word! Now, we must remember more and more distinct passwords as time passes, we age, accumulate assets, and more digital services appear. There was a time watching TV didn't require passwords. Now we got streaming, TV accounts and child lock - all with their own passwords. A password manager is only partially helpful -- it only helps with services that permit its usage (banking apps do not, for instance). Even with a password manager, you are left with hundreds of passwords to deal with as the 'occasional' password reset happens on a regular cadence.
This was forseen decades ago. Client certificates were one solution. A client certificate authenticates you one time (or uses your OS/device authentication). Then it authenticates you to a thousand different websites or devices using PKI. No passwords flow over the wire. The endpoint just imports your public certificate and links it to your user account. This technique is not limited to web browsers. You could add a friend's key to your intelligent door lock. His phone then unlocks your door by playing a sound to the lock's microphone - neither device needs an active network connection, and recording the sound would be useless to a hacker.
So, if security truly matters, why are browsers killing off client certificate authentication instead of doubling down on it and extending it to other domains?
More here: The Death (and Resurrection?) of Client Certificate Authentication