[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: Stefan Le Breton <stlb@xxxxxxxxxxxxxxx>
- Date: Tue, 28 Sep 1999 10:15:20 +0200
- Delivered-to: ircd-users-out@irc.org
- Delivered-to: ircd-users@irc.org
- In-reply-to: <37F065E2.D07CA20E@enterprise.net>; from wnelson on Tue, Sep 28, 1999 at 07:53:22AM +0100
- 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> <37F065E2.D07CA20E@enterprise.net>
On Tue, Sep 28, 1999 at 07:53:22AM +0100, wnelson wrote:
> 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....
Maybe those clients are detectable by unused USER arguments
(say "USER adec[- foo bar :sfvSDFC[]") but i doubt it.
^^^ ^^^
stefan