![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() - please write in English which sounds sense (orthography should be recognizable) - no rumours, no clan-news (except larger events) - always with list of reference/originator - please create compact news, 4-10 lines, colors, bold and cursive fontype is allowed (*) We decide finally which news will be published or not. Not published news remains here only if it is acceptable. |
![]() - bitte vernünftiges Deutsch mit erkennbarer Rechtschreibung ;) - keine Gerüchte, keine Clannews (ausgenommen größere Veranstaltungen) - immer mit Quellen- oder Urheberangabe - bitte kompakte News, 4-10 Zeilen, Farbe, fett, kursiv möglich (*) Wir entscheiden letztlich, welche News veröffentlicht wird und welche nicht. Nicht veröffentlichte News bleiben hier in diesem Forum bestehen, es sei denn sie sind für uns inakzeptabel. |
![]() - lisible et sans fautes ;) - pas de "on dit", pa de news des clans (sauf les grandes manifs) - toujours citer les sources - essaies de faire compact, 4 - 10 lignes, couleur, gras possible (*) On decide a la fin, laquelle des news va etre publie und laquelle non. News non publies restent dans ce forum, sauf si elle est inacceptable! |
![]() |
Guest_Dutchman_* |
![]()
Post
#1
|
Guests ![]() |
Hi,
since a few months there is a exploit floating around abusing the getstatus requests to launch dos attacks against random targets and as a side effect creating massive lags on clients and the server. Cause of this Yada from Staatsschutz.org made a patch for linux wich reduces the effectivity of this exploit. QUOTE etfix_getstatus 0.2 by yada / staatsschutz.org / jan. 2011 ------ This patch will ratelimit etded.x86 2.60b getstatus requests to 1 per IP every 4 seconds. This approach is not ideal as the real fix would be to change the protocol to require some kind of handshake but this would break compatibility with existing clients so its not really practical. The worst part is that the patch is (in theory) vulnerable to a dos where legitimate clients could be denied access to the getstatus command but i feel this is less of a headache than kiddies using the server to flood random targets and thereby lagging the server and pushing bandwith usage through the roof (master server is excluded from ratelimit so no need to worry about it being denied using spoofed packets). Download the file right here. A readme.txt, the sourcecode and a small howto are included. Your free to distribute this file. This post has been edited by Dutchman: Jan 6 2011, 11:33 AM |
|
|
![]() |
![]()
Post
#2
|
|
![]() Group: Members Joined: 25-December 09 Member No.: 89191 ![]() |
I just recently had to answer that question to someone else and I think came up with a rather simple example.
Suppose you have a mail box infront of your house. Every day you check the letters. There are some "spam" mails in there every day, so you sort them out right away and trash them, without even reading (or answering) them. However, you cannot stop people from putting spam letters into your mailbox. It's the same with software firewalls. You can prevent your server from "reading/answering" the packet, but it will still reach your machine (be put in its "mailbox"). There is nothing you can do about that, unless you control the upstream router (which you don't). Hope this example clarifies the situation to people who might have not understood before. |
|
|
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 1st July 2025 - 11:02 AM |