From: Daniel Lopes <lopsch@lopsch.com>
To: netfilter@lists.netfilter.org
Subject: Re: blocking irc + botnets
Date: Tue, 02 Aug 2005 18:55:39 +0200 [thread overview]
Message-ID: <42EFA58B.6000207@lopsch.com> (raw)
In-Reply-To: <bc5becf6050802084137a7ad69@mail.gmail.com>
hbeaumont hbeaumont schrieb:
> Can anyone help me with the proper method to block outgoing requests to
> botnets + irc?
>
> Or point me in the direction of searchable list archives (I could only find
> the non-searchable archives) or other FAQ that answers this?
>
> Problem:
>
> We have servers that could get infected via poorly wrote user scripts. I
> want to prevent these servers from being used as part of botnets or general
> connections to
> IRC (most scripts I run across seem to try to connect to IRC). I want to
> take the best preventative measures I can in case one of the machines would
> become infected
> or otherwise compromised.
>
> Also, interested in any other popular method of stopping general outgoing
> DOS attacks (rate limiting UDP perhaps? I'm not real up on the techniques
> used by the DOS'ers).
>
> I'm interested in the recommended rules to add to prevent this type of thing
> should it occur. Thanks.
>
>
You should block the appropriate IRC portrange. Additionally you could
mark IRC packets with l7 matching and then drop them afterwards. I think
this will filter pretty much of the IRC traffic, perhaps all.
next prev parent reply other threads:[~2005-08-02 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 15:41 blocking irc + botnets hbeaumont hbeaumont
2005-08-02 16:55 ` Daniel Lopes [this message]
2005-08-02 18:36 ` R. DuFresne
2005-08-03 16:18 ` Maxime Ducharme
2005-08-04 7:43 ` Jan Engelhardt
2005-08-04 17:04 ` hbeaumont hbeaumont
2005-08-04 21:59 ` curby .
2005-08-05 6:26 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 16:37 Piszcz, Justin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42EFA58B.6000207@lopsch.com \
--to=lopsch@lopsch.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.