Live data from Hacker News

Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

herrjemand.medium.com

141–150 of 294 posts

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#141

I hate this new web where you're automatically assumed to be some malicious actor only because you don't accept cookies and strange third party code and then have to jump through hoops to show that you're not some evil bot. To be honest, if a website immediately throws some Cloudflare anti-DDoS thing in my face I don't even bother anymore.

I agree. Browsing the web can be super frustrating when there is a CAPTCHA every other page.

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#142
Reading CF's blog announcement [1], this is really horrifying. It trains users to insert security keys and accept biometric identification requests when visiting random web pages, on random untrusted domains.

This cannot possibly end well.

[1]: https://blog.cloudflare.com/introducing-cryptographic-attest...

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#143

Cloudflare captchas in particular, and any checks and roadblocks to see something publicly available in general, are terrible, period. It doesn't matter which form they take. Every time you see one you feel like a second-class citizen and get reminded that the internet is no longer what it used to be. I personally simply close the tab when I see a cloudflare "one more step" page.

How do you mitigate ddos attacks and other bad actors hitting a page? What does your cdn solution look like? Route optimization from your (single) endpoint to clients literally half a world away?

As I user, I simply don't care. I repeatedly get punished for doing nothing wrong. It's almost like airport security.

> What does your cdn solution look like?

> Route optimization from your (single) endpoint to clients literally half a world away?

And as a developer, I don't understand this newfangled obsession over CDNs either. Yes, there will be 200 ms RTT in some cases. So what? Get over it. Optimize your website to load in fewer round-trips. TCP congestion control adapts well enough to any latency. RTT only really matters in gaming and VoIP.

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#144
post #72

Earlier quoted context omitted.

Respectfully, I think you miss the point. The fact that 98% of traffic goes trough this new infrastructure, allows some still plug their server to the net raw and their traffic still gets trough.

>The fact that 98% of traffic goes trough this new infrastructure Doesn't mean that 98% of the value of the Internet results from this traffic. Even if you discount all of the web, there still lots of applications using the federated model (e.g. SMTP) or peer-to-peer (e.g. Crypto, VOIP), that require end-to-end connectivity.

You expand this discussion into completely new direction.

My original point is about capacity and if the old internet could work today. It seems like I'm correct, but I'm not so sure. I would like to see other opinions.

Every response so far is "there exists". The real issue is if the internet could do everything without caching data near the edge.

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#145
Can a FIDO key be implemented in software? Can you write a program to register a FIDO key as a multi-factor authentication device with a Google account?

Or is there some repository of all allowed devices with identifiers? Intuitively that'd be the only way to prevent infinite virtual devices..

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#146

Earlier quoted context omitted.

How do you mitigate ddos attacks and other bad actors hitting a page? What does your cdn solution look like? Route optimization from your (single) endpoint to clients literally half a world away?

As I user, I simply don't care. I repeatedly get punished for doing nothing wrong. It's almost like airport security. > What does your cdn solution look like? > Route optimization from your (single) endpoint to clients literally half a world away? And as a developer, I don't understand this newfangled obsession over CDNs either. Yes, there will be 200 ms RTT in some cases. So what? Get over it. Optimize your website…

I don't think you understand why that captcha is there in the first place then.

Cloudflare prevents a bunch of crap that site operators just don't want to deal with. Especially for smaller sites that are run by one person. Dealing with a wordpress site getting hacked because you missed an update by a day, or a bulletin bored getting swarmed with bots, or some asshat ddos'ing your site because you banned them. Suddenly that site just isn't worth running.

Complaining that about a thing that prevents that headache because it's a minor inconvenience to you is so self centered it boggles the mind.

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#147

Earlier quoted context omitted.

How do you mitigate ddos attacks and other bad actors hitting a page? What does your cdn solution look like? Route optimization from your (single) endpoint to clients literally half a world away?

As I user, I simply don't care. I repeatedly get punished for doing nothing wrong. It's almost like airport security. > What does your cdn solution look like? > Route optimization from your (single) endpoint to clients literally half a world away? And as a developer, I don't understand this newfangled obsession over CDNs either. Yes, there will be 200 ms RTT in some cases. So what? Get over it. Optimize your website…

that 200ms rtt does matter to users. it becomes very noticeable. especially when you're writing an app, not a brochure site. You need to tree shake so you're not serving a huge spa all at once.

I've see much worse times for users, and a cdn absolutely help with our staff in asia dealing with our internal apps.

Of course they're not always tripping up cloudflare and being shown captchas. I almost _never_ see a cloudflare captcha either... huh...

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#148

Earlier quoted context omitted.

As I user, I simply don't care. I repeatedly get punished for doing nothing wrong. It's almost like airport security. > What does your cdn solution look like? > Route optimization from your (single) endpoint to clients literally half a world away? And as a developer, I don't understand this newfangled obsession over CDNs either. Yes, there will be 200 ms RTT in some cases. So what? Get over it. Optimize your website…

I don't think you understand why that captcha is there in the first place then. Cloudflare prevents a bunch of crap that site operators just don't want to deal with. Especially for smaller sites that are run by one person. Dealing with a wordpress site getting hacked because you missed an update by a day, or a bulletin bored getting swarmed with bots, or some asshat ddos'ing your site because you banned them. Suddenl…

Yeah, so centralizing the entire internet around a black box that sees all your traffic in cleartext is clearly the right solution. /s

> Dealing with a wordpress site getting hacked because you missed an update by a day

Maybe don't use something this vulnerable then and rely on a third party to protect you from exploits.

> or a bulletin bored getting swarmed with bots

Maybe require email verification and/or a captcha when signing up or posting. Don't punish people for passive actions.

Somehow, there are many forums that aren't behind cloudflare, yet there are no spam bots.

> or some asshat ddos'ing your site because you banned them

Sure ddos is such an everyday occurrence?

I just don't understand. I run a personal website. There's literally nothing to "deal" with. I set it all up once and it works. I only have to pay for the server and for the domains on time.

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#149
post #138

Earlier quoted context omitted.

No offense, this framing is so dumb. I hate it. The ‘Internet 3.0’ isn’t coming because of Cloudflare. It’s coming because these monolith big tech companies have an army of engineers who have been centralizing and building it this way for years. Cloudflare didn’t build these walls, it’s more of a giant boat now navigating it because other companies have no choice. I like to think of them as giant data ferryman in thi…

Clearly Cloudflare isn't responsible for the data centralization that is corrupting the internet. They are however, a very sophisticated and efficient enforcer of those policies. They've helped ensure large portions of the web is no longer crawlable, and that serves to consolidate information and power in those tech monopolies.

Aka, SMB's now have access to the same tools the tech monopolies do.

GDPR-like policies will continue to flood as governments partition their Internets and data making it harder and harder to run international Internet businesses.

I'm not particularly happy about things either (especially crawling access), but it will be a net positive whenever you can level the playing field with competition.

When the biggest infringers of data are driving the creation of government policies that only they can circumvent and navigate -- that's a serious, serious problem.

Re: Cloudflare’s CAPTCHA replacement with FIDO2/WebAuthn is a bad idea

#150

Reading CF's blog announcement [1], this is really horrifying. It trains users to insert security keys and accept biometric identification requests when visiting random web pages, on random untrusted domains. This cannot possibly end well. [1]: https://blog.cloudflare.com/introducing-cryptographic-attest...

Isn't part of the point is that a phishing site wouldnt get the same response as a legit site, and therefore it's be useless to do that, so this behavior is ok?
Post reply on HN