2 ms·
We don't do Client Certs because the problem is now you're asserting an identity. So what's the identity? Maybe I'm happy for Hacker News and GitHub to know me
by tialaramex 8y ago
We don't do Client Certs because the problem is now you're asserting an identity. So what's the identity?
Maybe I'm happy for Hacker News and GitHub to know me as Nick Lamb, but I'd prefer that Grindr thinks of me as Steve Farmer, so that's now an additional certificate and then some sort of choice mechanic so I pick the right one. And if I screw up, or an advertising network is able to tie these identities together I can't undo that.
WebAuthn create a scenario where you can prove to a site that _you_ still have the same FIDO token as when _you_ signed up. But they don't get anything else, you have to mount an _active attack_ to even find out whether the token Alice shows you when she logs in is really the same token that Bob shows when he logs in, or to find out whether the credentials you've stolen from Facebook for alice@example.com are for the same token that Bob is using on GitHub. Passive attacks can't find any of that out, and remember each active attack attempt causes a physical human interaction, you can't just write a Javascript to try it a billion times until it succeeds.
- marmot777 8y agoYes. Good point. Identity isn't ipso facto legit.