software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000933.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] ircservices-5 feature request
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ircservices-5%20feature%20request&In-Reply-To=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="000929.html">
  11    <LINK REL="Next"  HREF="000930.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] ircservices-5 feature request</H1>
  15     <B>Aragon Gouveia</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ircservices-5%20feature%20request&In-Reply-To="
  17        TITLE="[IRCServices Coding] ircservices-5 feature request">aragon at phat.za.net
  18        </A><BR>
  19     <I>Fri Jun 21 12:34:49 PDT 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000929.html">[IRCServices Coding] Call for translators
  22 </A></li>
  23         <LI>Next message: <A HREF="000930.html">[IRCServices Coding] Services 5.0pre3 released
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#933">[ date ]</a>
  27               <a href="thread.html#933">[ thread ]</a>
  28               <a href="subject.html#933">[ subject ]</a>
  29               <a href="author.html#933">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Hi,
  35
  36 This is a big one. I'd like to know if it'd be possible to add regular
  37 expression akill-add support to version 5 (via a module?).
  38
  39 I'd like to be able to define regex patterns that cause regular akills to be
  40 automatically added when matched. The regex checking must be based on
  41 nickname, ident, hostname, and gecos. Would it also be possible to have a
  42 regex exception list too... so if a client matches a regex pattern, but also
  43 matches one of the exceptions, it doesn't get akilled.
  44
  45 I'm kinda implementing this at the moment using a client type bot that
  46 receives local and remote connect notices. I use it to get rid of those
  47 pesky mass flood bots that are so popular these days. I know, you're
  48 probably thinking I should be doing open proxy scans. I do :). But a lot
  49 still get through.
  50
  51 The big advantage of services doing this is that you can match based on
  52 gecos (for added accuracy) and it's much faster. My bot sends a privmsg to
  53 operserv when it finds a match adding *@hostname to the akill list with a
  54 hard coded expiry of 150 days.
  55
  56 What do you think?
  57
  58
  59 Thanks,
  60 Aragon
  61
  62
  63
  64 </PRE>
  65
  66 <!--endarticle-->
  67     <HR>
  68     <P><UL>
  69         <!--threads-->
  70         <LI>Previous message: <A HREF="000929.html">[IRCServices Coding] Call for translators
  71 </A></li>
  72         <LI>Next message: <A HREF="000930.html">[IRCServices Coding] Services 5.0pre3 released
  73 </A></li>
  74          <LI> <B>Messages sorted by:</B>
  75               <a href="date.html#933">[ date ]</a>
  76               <a href="thread.html#933">[ thread ]</a>
  77               <a href="subject.html#933">[ subject ]</a>
  78               <a href="author.html#933">[ author ]</a>
  79          </LI>
  80        </UL>
  81
  82 </body></html>