4 ms·
Yes, Tor services are particularly easy to DoS and there's pretty much nothing the DoS recipient can do about it.
by prvit 4y ago
Yes, Tor services are particularly easy to DoS and there's pretty much nothing the DoS recipient can do about it.
- noasaservice 4y agoWell, other than deregistering the onion address from dHT and quit :) I'm glad their little "community" is being seen off into the void. Good riddance.
- tsujamin 4y agolooks like it took down a related nz neo-nazi site too > The ban may have also inadvertently blocked a New Zealand-based neo-nazi group called Action Zealandia. > The Action Zealandia website, which is believed to be hosted by a website run by Moon, is also offline. (https://www.newshub.co.nz/home/technology/2022/09/infamous-kiwifarms-website-blocked-by-cyber-security-firm-over-escalating-threats.html https://www.newshub.co.nz/home/technology/2022/09/infamous-k...)
- ogurechny 4y agoComments like these really make me see it as another Internet Battle of one group of dedicated assholes against the other group of dedicated assholes.
- LinuxBender 4y agoIf they have the time and are willing to put in the effort, they can create a myriad of Tor onion servers that are just nginx proxy-cache nodes that forward over a VPN mesh to their application servers. The end-users would have to be aware of all the onion cache servers somehow or their application would have to load balance people across them and keep some unannounced and cycle some in and out.
- prvit 4y agoThis isn't meaningfully different from using onionbalance, the attackers will still be at a significant advantage.
- LinuxBender 4y agoI know what you mean and somewhat agree. I don't know much about KF but I assume they probably have subforums and groups of people within those forums. What I have seen people do in the past is set up what I described above and then share half of the random cache nodes with the general public and then share specific nodes with sub-groups of people keeping the site accessible to the regular or trusted users. The public cache nodes can have stricter limits on how many requests are forwarded over the VPN. Perhaps this is not compatible with KF's model. I've never seen their site aside from the CF error message.