3 ms·
Because client certificates have been around for donkeys years and almost nobody uses them. Even technical people! But technical people do use ssh keys.
by nodata 12y ago
Because client certificates have been around for donkeys years and almost nobody uses them. Even technical people!
But technical people do use ssh keys.
- IgorPartola 12y agoFeels like the case for that XKCD about standards.
- stephenr 12y agoEven technical people can make stupid mistakes. Look at MongoDB and it's legion of fans.
- DanBC 12y ago> Even technical people can make stupid mistakes. > it's ahem
- stephenr 12y agoSomehow I don't qualify a misplaced apostrophe (either by human error or bad autocorrect) on the same scale as choosing a fundamentally bad database or failing to understand/take advantage of powerful technologies such as client side certificates.
- xtracto 12y agoWe use client certs in the company where I work to authenticate into all internal pages. Once the infrastructure was in place (an easy way to generate a certificate to any new colleague) it has been a breeze to setup and use. Server side, it is 3 or 4 Nginx lines. Client side, people only have to get the cert, click it to open, and install it on Chrome. After that, they are happy they don't have to remember any password for our different services. I think we could implement it for our users if we gave the option to "login using cert" and "send me a new cert" (to the email they used for signin). People need minimal training but they don't have to be computer literate to do it (half of our company are not, and they found it better than passwords once the system was in place).