4 ms·
Even if we ignore the technical reasons, for me CloudFlare's proposal fails at their "Associate a unique ID to your key" property, where they say CloudFlare cou
by viraptor 6y ago
Even if we ignore the technical reasons, for me CloudFlare's proposal fails at their "Associate a unique ID to your key" property, where they say CloudFlare could, but won't do it. If they implement this scheme they start normalising this approach. Once it gets to FB and Google implementation, their answer will be: we could, but we... look! a squirrel!
- tialaramex 6y agoTheir document says, correctly, that the means by which they could try to do this would be to shove the arbitrary random ID they get into a cookie. You may have noticed that both Facebook and Google already use cookies. Did you know Hacker News has a cookie too?
- userbinator 6y agoDid you know Hacker News has a cookie too? There's a difference between being logged in to an account on a single site, and letting Big Tech track you across most of the Internet.
- tialaramex 6y agoWebAuthn isn't "letting Big Tech track you" which is why, as Cloudflare explains, they would need to store the ID in a cookie to remember what it is. You might be thinking "Duh, they can ask the Security Key". Nope, the Security Key hasn't the faintest idea, remembering that ID is the Relying Party's job, the Security Key isn't going to remember.