I’d rather take these tradeoffs than doing 5 steps of Recaptcha because I’m using a VPN to work, which as Cloudflares announcement said, is very localized to North America and likely extra complicated for those outside the region. In theory, couldn’t Yubikey begin reducing batch sizes to 1,000 and Cloudflare mark specific batch numbers as requiring one extra step to verify? The vast majority of Yubikey sales will be…
Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
11–20 of 294 posts
Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#12Great in that they have a fantastic UI to add your site in, basically shielding the average user from attacks.
Bad from a standpoint of that now only Google, Bing, and maybe other big search engines have the capabilities to actually crawl the internet now.
I don't see us getting a massive innovation in search on the internet now that Google has such a massive foothold, and companies like Cloudflare stop innovation from happening.
Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#13Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#14Earlier quoted context omitted.
I believe the idea here is you need to buy actual FIDO U2F keys and they could then be revoked on a per-key basis if you're caught abusing them as they're signed by a 3rd party so can't just be emulated. Meaning you need to buy more. Makes it expensive at least.
But i'm specifically asking about software. I know Touch ID can be used with WebAuthn and also see the DevTools in chrome WebAuthn debugger. Just seems easy to fool when I regenerate a key on every visit unless there is additional step I don't get.
Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#15Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#16Earlier quoted context omitted.
I believe the idea here is you need to buy actual FIDO U2F keys and they could then be revoked on a per-key basis if you're caught abusing them as they're signed by a 3rd party so can't just be emulated. Meaning you need to buy more. Makes it expensive at least.
How can you revoke on a per-key basis without at the same time being able to track keys uniquely?
Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#17Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#18Earlier quoted context omitted.
But i'm specifically asking about software. I know Touch ID can be used with WebAuthn and also see the DevTools in chrome WebAuthn debugger. Just seems easy to fool when I regenerate a key on every visit unless there is additional step I don't get.
You can't generate an attested key with the devtools. It won't be signed by a 3rd party that CloudFlare has approved.
Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#19Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea
#20Cloudflare is both a great thing and a terrible thing that has happened to the internet in recent years. Great in that they have a fantastic UI to add your site in, basically shielding the average user from attacks. Bad from a standpoint of that now only Google, Bing, and maybe other big search engines have the capabilities to actually crawl the internet now. I don't see us getting a massive innovation in search on t…
How are we "stopping search innovation"?