<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1"><font face="Verdana">Sorry if my reply sounded rude
;)<br>
<br>
Was not implying that :)<br>
<br>
What I meant is that with iptables i filter also the
"statusResponse" requests... that's done for logging (I recently
got hit as a target and yes... that was hard ...) I think that
reporting the hosts attacking me to their relevant abuse desks
is the way to go...<br>
Logging the reflectos can be helpful ;)<br>
<br>
But I agree that done at application level is stressful and not
every useful :)<br>
<br>
Still I cannot believe the big market players are still being
used to launch attacks... and I hope that at least the abuse
desks of their upstream suppliers will be able to do something
-_-'<br>
</font></font><br>
Il 12/11/2011 08:05, Ryan C. Gordon ha scritto:
<blockquote cite="mid:4EBE1AD6.5070101@icculus.org" type="cite">
<br>
<blockquote type="cite">I do not think these patched binaries
keeps blacklist also in case of
<br>
target of an attack too (statusResponse)
<br>
</blockquote>
<br>
The goal of the patch is to prevent others from using your CoD4
server to spam a third party, by spoofing their IP address. A
blacklist wouldn't be useful here, especially if they are
targeting legitimate (and innocent) COD4 players.
<br>
<br>
We also aren't able to stop people from flooding _your_ server
with unwanted packets; a blacklist isn't really helpful here,
either.
<br>
<br>
--ryan.
<br>
<br>
_______________________________________________
<br>
cod mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:cod@icculus.org">cod@icculus.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://icculus.org/mailman/listinfo/cod">http://icculus.org/mailman/listinfo/cod</a>
<br>
</blockquote>
</body>
</html>