So your argument is because there are reflection attacks with higher
amplification, Valve should, do nothing?
I don't think anyone is worried about carriers or datacenters going down
over source engine reflection attacks, and I made no comment that would
imply that.
My goal is to keep customer's services//online throughout the attacks,
regardless of method or size. DNS/NTP/SNMP reflections are far less
resource intensive to mitigate compared to attacks that require
hashlimits or DPI, even if they are magnitudes larger on average.
I'm not sure why anyone would condemn Valve for patching a well known
reflection vector.
What are you talking about 😂
There's millions of other boxes. The genesis for all of this was SNMP
+- NTP, which came after and was 50x worse per academia. NTP, SNMP,
and CoD were the basic reflection staples of 2010.
There's MTU hacks that break other queries which further destroy the
ecosystem regarding statistics. Breaking outside of the hacked STB
ecosystem (and oh my lord is there a lot) this is not really a hot
market anymore. There's boxes that can actually saturate the entire
link now that don't have to spoof. My single port server receiving on
27015 killing an entire datacentre (which hit many other folks - to
the point of pings on IRC) from getting a simple reflection attack is
long gone.
Basically, it's great that you've found the entire Valve + self-hosted
ecosystem at its peak. But this is a decade old issue that no longer
impacts real carriers,
Kyle.
On Mon, Nov 16, 2020 at 6:43 PM Calvin Judy - calvin at swiftnode.net
(via csgo_servers list) <[email protected]> wrote:
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/
