6 ms·
There's one thing about client certs that people should be aware: They open up new security and privacy issues. There have been a number of TLS protocol issues
by hannob 11y ago
There's one thing about client certs that people should be aware: They open up new security and privacy issues.
There have been a number of TLS protocol issues regarding client certificates that didn't receive that much attention (Triple Handshake, SLOTH), because not that many people use clientcerts. That's not really an argument against them, but it's a hint that if we want to use them more widely things would probably need more scrunity in security analysis.
Another issue that worries me more: Client certificates can break privacy expectations. The reason is that the cert is not hidden from the traffic. This makes the traffic less privacy preserving than - let's say - a simple password, because the password is hidden inside the TLS encryption stream, while the client certificate is not. I think users have a reasonable expectation that "if I only surf HTTPS sites nobody sees any personally identifiable information from me, just the sites I'm surfing". Client certificates break this expectation.
- true_religion 11y agoIf you do EV, a client side cert will reveal a lot--essentially shouting your real name and address to every router between you and the server. However, what about self-signed certs?
- cpach 11y agoIs EV really available for client certs?
- tnndk 11y agoIn TLSv1.3 the privacy issue is fixed. The client certificate is sent encrypted. And also, the client certificate doesn't have to be sent in the beginning of the session.