[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: We have a major trouble
- To: ircd-users@xxxxxxx
- Subject: Re: We have a major trouble
- From: wnelson <wnelson@xxxxxxxxxxxxxx>
- Date: Tue, 28 Sep 1999 07:53:22 +0100
- Delivered-to: ircd-users-out@irc.org
- Delivered-to: ircd-users@irc.org
- References: <19990926133618.A12989@mgc.spacestar.net> <19990927065043.B434@stealth.net> <19990927092357.D19031@mgc.spacestar.net> <19990927184646.W28983@sgh.waw.pl> <19990927115411.O19280@mgc.spacestar.net> <19990927120912.P19280@mgc.spacestar.net> <19990927142554.A2142@stealth.net>
Christophe Kalt wrote:
> On Sep 27, Gael M . wrote:
> | but this 4000 shits can send commands like stats or else on all server
> | i m not sure servers won t split after that...
> this amount of clones can easily hurt any single server, any
> link, anything.
> there isn't much that can be done about it either.
Ok - I'm not sure how feasible this idea would be, but is there any way
a service of some kind could be used to check connections for a
trojan-like response? What that response would be and what to do if
infected clients are detected though, I don't know....