3 ms·
Because paired keys aren't user friendly to a non-developer. Which is most people in the world.
by minimaxir 13y ago
Because paired keys aren't user friendly to a non-developer. Which is most people in the world.
- samuellevy 13y agoIn the current incarnation, no they're not, but built into the browser? The user wouldn't need to see anything more than a "sign in with you private key" button, next to the "sign in with google" button.
- OafTobark 13y agoYou assume that would remove confusion. If anything it might add to it.
- BoyWizard 13y agoHandling them in the browser is a good idea, but still needs a lot of work to make it workable: - What happens when their computer crashes? - How do they transfer these certificates to other devices (multiple computers, phones, tablets, etc)? - How do they keep them in sync across multiple devices if they need to regenerate the certificate? - Certificates would be super easy to steal once you get access to a device (arguably easier to steal than installing a keylogger to get passwords) The only way I can see it working for most users is through a third-party management solution (Google, iCloud, whatever).