cross-posted from: https://lemmy.dbzer0.com/post/1491194
I would love if just once an admin of a fedi host under DDoS attack would have the integrity to say:
“We are under attack. But we will not surrender to Cloudflare & let that privacy-abusing tech giant get a front-row view of all your traffic while centralizing our decentralized community. We apologize for the downtime while we work on solving this problem in a way that uncompromisingly respects your privacy and does not harm your own security more than the attack itself.”
This is inspired by the recent move of #LemmyWorld joining Cloudflare’s walled garden to thwart a DDoS atk.
So of course the natural order of this thread is to discuss various Cloudflare-free solutions. Such as:
- Establish an onion site & redirect all Tor traffic toward the onion site. 1.1. Suggest that users try the onion site when the clearnet is down— and use it as an opportunity to give much needed growth to the Tor network.
- Establish 3+ clearnet hosts evenly spaced geographically on VPSs. 2.1. Configure DNS to load-balance the clearnet traffic.
- Set up tar-pitting to affect dodgy-appearing traffic. (yes I am doing some serious hand-waving here on this one… someone plz pin down the details of how to do this)
- You already know the IPs your users use (per fedi protocols), so why not use that info to configure the firewall during attacks? (can this be done without extra logging, just using pre-existing metadata?)
- Disable all avatar & graphics. Make the site text-only when a load threshold is exceeded. Graphic images are what accounts for all the heavy-lifting and they are the least important content. (do fedi servers tend to support this or is hacking needed?)
- Temporarily defederate from all nodes to focus just on local users being able to access local content. (not sure if this makes sense)
- Take the web client offline and direct users to use a 3rd party app during attacks, assuming this significantly lightens the workload.
- Find another non-Cloudflared fedi instance that has a smaller population than your own node but which has the resources for growth, open registration, similar philosophies, and suggest to your users that they migrate to it. Most fedi admins have figured out how to operate without Cloudflare, so promote them.
^ This numbering does /not/ imply a sequence of steps. It’s just to give references to use in replies. Not all these moves are necessarily taken together.
What other incident response actions do not depend on Cloudflare?
All the more reason to get your security house in order before rolling out service. If security is an afterthought, you’re doing it wrong.
Users don’t even know they’re being pawned to a US tech giant, so their expectations are not even being realized at this point. IOW, these user /expectations/ that are driving your point are that of uninformed users.
This instance that you are posting to is in fact run by a guy who has proven to thwart DDoS attack without resorting to CF using methods 1 and 3 (confirmed), perhaps more.
On the contrary, it’s the “let’s have Cloudflare centralize everything” attitude that’s “not conducive to open conversation”. You are crashing in on a constructive discussion just to piss in the wind and stifle a constructive discussion.
The folks who would be annoyed or dismissive of efforts to counter attacks without being pawned by Cloudflare are not the intended audience here.
Yikes. Telling people “bring a PR or GTFO” is very much the non-constructive shitty attitude we need to avoid. Discussion happens before implementation. Only a fool implements before design. Design is best when it has community feedback.
I’m glad to hear it. Did they share these solutions in an easy-to-consume manner for other instance admins who may not have the same expertise, resources, or time? As I said before, I’m not suggesting they must do the work to share these things in an easy-to-consume manner - I’m just saying if these solutions aren’t available in an easy to consume manner, then you shouldn’t be so surprised and upset that other people are reaching for the easy-to-use solutions instead.
The sentence you quoted very specifically did not say “bring a PR or GTFO,” so I’ll ask that you try to not put words in my mouth. In fact, I went to great lengths to make it clear I wasn’t saying that because I happen to agree with you - it is an unconstructive attitude.
I very specifically did say “bring a PR or don’t get mad that other people aren’t immediately doing the work for you.” If you aren’t bringing a PR then you are bringing an idea. If you aren’t bringing solutions but are bringing a sensationalist and confrontational attitude, don’t be surprised when you have a confrontation rather than a conversation.
Maybe it would be more constructive to identify barriers to adopting privacy-respecting solutions rather than getting judgemental about using other solutions. What makes Cloudflare easier than tarpitting? How could the barrier to adopting tarpitting be lowered to make it a reasonable solution to adopt? Are there any Lemmy admins that can weigh in on the conversation and share their challenges?