software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002947.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Another Feature Suggestion
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Another%20Feature%20Suggestion&In-Reply-To=20020531120513.A14632%40rucus.ru.ac.za">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="002946.html">
  11    <LINK REL="Next"  HREF="002949.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Another Feature Suggestion</H1>
  15     <B>Russell Garrett</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Another%20Feature%20Suggestion&In-Reply-To=20020531120513.A14632%40rucus.ru.ac.za"
  17        TITLE="[IRCServices] Another Feature Suggestion">rg at tcslon.com
  18        </A><BR>
  19     <I>Fri May 31 12:17:00 PDT 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002946.html">[IRCServices] Another Feature Suggestion
  22 </A></li>
  23         <LI>Next message: <A HREF="002949.html">[IRCServices] Another Feature Suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2947">[ date ]</a>
  27               <a href="thread.html#2947">[ thread ]</a>
  28               <a href="subject.html#2947">[ subject ]</a>
  29               <a href="author.html#2947">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> I disagree with this.  A lot of the unwanted bots that
  35 </I>&gt;<i> I've seen have
  36 </I>&gt;<i> patterns in their nicks.  I tend to Q-line the pattern as
  37 </I>&gt;<i> soon as I work out
  38 </I>&gt;<i> what it is.  At the moment I have things like [HarD]*,
  39 </I>&gt;<i> *GuNBot, [ADLF]*,
  40 </I>&gt;<i> al^jekr*, [AceBots]*, etc Q-lined in my ircd.conf.
  41 </I>&gt;<i>
  42 </I>&gt;<i> The idea of being able to clean up with a regex or
  43 </I>&gt;<i> wildcard based kill is
  44 </I>&gt;<i> somewhat appealing to me for this reason.
  45 </I>
  46 Ok I see your point :). Most of the clonebot attacks I've seen
  47 however can be stopped more efficiently by catching them as they join
  48 the network using OperServ session limiting and proxy scanning. The
  49 concievable third way would be using trojans to infect users
  50 computers and use them as bots in a clonebot attack. I haven't seen
  51 one of these myself, but this method couldn't be caught by session
  52 limiting or proxy scanning, so I suppose you've just got to hope for
  53 a pattern in them.
  54
  55
  56 Russ Garrett
  57 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">russ at garrett.co.uk</A>
  58 www.faereal.net
  59
  60
  61 </PRE>
  62
  63 <!--endarticle-->
  64     <HR>
  65     <P><UL>
  66         <!--threads-->
  67         <LI>Previous message: <A HREF="002946.html">[IRCServices] Another Feature Suggestion
  68 </A></li>
  69         <LI>Next message: <A HREF="002949.html">[IRCServices] Another Feature Suggestion
  70 </A></li>
  71          <LI> <B>Messages sorted by:</B>
  72               <a href="date.html#2947">[ date ]</a>
  73               <a href="thread.html#2947">[ thread ]</a>
  74               <a href="subject.html#2947">[ subject ]</a>
  75               <a href="author.html#2947">[ author ]</a>
  76          </LI>
  77        </UL>
  78
  79 </body></html>