News for hackers. Stuff that matters.
Re:The State of HTTP in 2022 by zdragnar on Saturday December 31, 2022 @07:03PM (#34202082)
It isn't your security they're concerned about, it is the server's- it is preventing DDoS attacks.

If you want to blame someone, blame the people who poisoned the well for everyone else.

Re:The State of HTTP in 2022 by maxbond on Saturday December 31, 2022 @07:17PM (#34202175)
We can walk & chew gum here, spammers and DDoSers are poisoning the well for sure, but Cloudflare is responsible for externalities of their service.
Re:The State of HTTP in 2022 by georgyo on Saturday December 31, 2022 @08:06PM (#34202498)
> We can walk & chew gum here

I've never heard this expression before, but I think this expression works against you here.

Many cities have a problem with people putting gum on the sidewalks. Some cities have banned chewing gum to combat this. This is similar to cloudflare banning questionable clients.

More on topic, I understand the view point here, but cloudflare is better than the way things used to be. With the privacy pass extension, visit sites with the tor browser is pretty painless. It used to be all too common for sites to just outright ban all tor traffic.

Re:The State of HTTP in 2022 by zdragnar on Saturday December 31, 2022 @11:25PM (#34203590)
Server hosts want protection from DDoS. They hire a bouncer (I e. Cloudflare) to keep the hordes at bay. The bouncer asks for some way to distinguish your suspicious looking request from that of the start of a DDoS attack.

How is this an "externality" of cloudflare's service? If anything, it is an "externality" of the server hosts.

Re:The State of HTTP in 2022 by maxbond on Sunday January 01, 2023 @12:10AM (#34203797)
Does it even matter? Blame is irrelevant, I find responsibility to be a more interesting thing to discuss in virtually all circumstances. The DDoSers and spammers should cut it out (but unfortunately we can't really count on them for anything), Cloudflare should make more of an effort to preserve accessibility, and their customers should care about it too & make it clear to Cloudflare that it's a priority to them.

But if we take a step back it's clear that Cloudflare is the entity here that can have the biggest impact. Spammers and customers are diffuse, Cloudflare isn't. How much of the blame they deserve, I don't really care, but theres a problem, they're in the best position to act, so they have a responsibility to. In my opinion, that's the best mindset for solving problems.

Re:The State of HTTP in 2022 by zdragnar on Sunday January 01, 2023 @12:35AM (#34203918)
> Blame is irrelevant, I find responsibility to be a more interesting thing to discuss

This is, to me, a bizarre notion. You're imposing some sort of moral edict upon cloudflare for providing an opt-in service to web hosts.

> they're in the best position to act

They have, and they decided that certain traffic requires additional consideration to distinguish from bad actors. Your refusal to cooperate is entirely on you.

Just because you don't like their solution doesn't mean that there is a better one. If you have better ideas, I'm sure they're all ears, as less intrusive is generally cheaper to implement.

Re:The State of HTTP in 2022 by userbinator on Saturday December 31, 2022 @08:13PM (#34202539)
it is preventing DDoS attacks.

Is it? Those who want to DDoS will always find a way, and meanwhile users with slightly odd hardware/software are being locked out. Admittedly the latter is a minority, but one of the key tenets of the Internet and what made it so successful was interoperability. This is, in some ways, even worse than (but somewhat of a following effect of) the effective browser monopoly.

Calling it "security" when it's really about "availability" is another deceptive misdirection, because the former is something that can more easily persuade the sheeple.

I don't really like to go to extremes, but fingerprinting clients and deciding access based on such should really be regarded as a moral equivalent to racial profiling.

Re:The State of HTTP in 2022 by zdragnar on Saturday December 31, 2022 @08:19PM (#34202586)
Profiling happens all the time for entirely legitimate reasons in the real world. Racial profiling is immoral not because it is profiling; it is immoral because it is based on immutable characteristics which have no intrinsic bearing on the purpose of the profile.

To tie this back to the topic at hand, you're complaining that a service has decided your traffic resembles known patterns from bad actors, and is asking you to go through an extra step to access the content.

Are there better options? Maybe, but it's utterly asinine to compare what cloudflare is doing to racial profiling.

Re:The State of HTTP in 2022 by jayd16 on Saturday December 31, 2022 @08:53PM (#34202784)
> Those who want to DDoS will always find a way

How do you figure? You don't think far more DDoS events would occur if it was easier and more effective?

Re:The State of HTTP in 2022 by cortesoft on Saturday December 31, 2022 @09:17PM (#34202911)
> Those who want to DDoS will always find a way

Not really. We are actually pretty good these days at stopping DDOS attacks.

Re:The State of HTTP in 2022 by mysterydip on Saturday December 31, 2022 @09:23PM (#34202942)
Not sure how accurate this is, but currently shows 150+ DDoS attacks going on globally: https://www.netscout.com/ddos-attack-map
Re:The State of HTTP in 2022 by cortesoft on Saturday December 31, 2022 @09:48PM (#34203085)
DDOSes still happen a lot, but the infrastructure can mostly handle it ok.
Re:The State of HTTP in 2022 by acdha on Saturday December 31, 2022 @10:02PM (#34203154)
It’s accurate. That’s a marketing page for a DDoS prevention service so it’s not an unbiased source, and it’s especially important to remember the distinction between traffic hitting something like an edge node and actually reaching the target and causing harm. I see attacks fairly regularly (politics) but in most cases it means I see 15M block events for “GET /“ in Cloudflare’s dashboard but no actual impact on the service because they’re dropped quickly at locations around the world or, if they faked real browsers, they got a bunch of cache hits.

In other cases, people try more sophisticated attacks (e.g. posting random terms to a search page to avoid caching) and that’s more of a problem but it’s probably like 1% of the total traffic because it’s moved out of script kiddie territory into something where you need to have more skills and people don’t generally do that without a way to make money from it. One challenge with a DDoS in that regard is that it’s not subtle so your ability to wage an attack goes away relatively quickly without constant work replacing systems which are taken offline by a remote ISP.

Re:The State of HTTP in 2022 by xboxnolifes on Sunday January 01, 2023 @04:40AM (#34205001)
If we weren't pretty good at stopping DDoS attacks, every major hosting provider would be offline daily. Yet, websites being inaccessible for me is fairly uncommon.
Re:The State of HTTP in 2022 by acdha on Saturday December 31, 2022 @09:21PM (#34202936)
> Those who want to DDoS will always find a way

This is like saying no lock will stop a thief. Cost and difficulty matter, and requiring a full browser increases the challenge for an attacker enough that some people will give up and others won’t be able to send as much traffic. That’s not perfect but speaking from experience a surprising fraction of people will give up after a naive attack fails.

Re:The State of HTTP in 2022 by worldofmatthew on Sunday January 01, 2023 @03:39AM (#34204719)
DDOS attacks that exist because Cloudflare knowly protects booter websites which feeds the DDDOS economy with money to make DDOS botnets profitable?