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

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] My ideas for WAKILL
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20My%20ideas%20for%20WAKILL&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="003399.html">
  11    <LINK REL="Next"  HREF="003401.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] My ideas for WAKILL</H1>
  15     <B>calimonk</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20My%20ideas%20for%20WAKILL&In-Reply-To="
  17        TITLE="[IRCServices] My ideas for WAKILL">calimonk at gmx.net
  18        </A><BR>
  19     <I>Thu Dec 12 11:10:01 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003399.html">[IRCServices] sqline reason not working...
  22 </A></li>
  23         <LI>Next message: <A HREF="003401.html">[IRCServices] My ideas for WAKILL
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#3400">[ date ]</a>
  27               <a href="thread.html#3400">[ thread ]</a>
  28               <a href="subject.html#3400">[ subject ]</a>
  29               <a href="author.html#3400">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Hey everyone,
  35
  36 Just a brainstorm i had, here goes. (Excuse bad spelling i had a rough sleep)
  37
  38 WAKILL... What the hell is WAKILL you might ask, let me explain.
  39
  40 Recently i've noticed that 'standard' akills just won't be able to ban what
  41 we need, so i figured we need akills with 'more' or 'better' wildcards.
  42
  43 If not for instance, bots connect with QKGJLKSD, QKLGJLKE, QLKTEFDF,
  44 QGKLJEGS as ident and all random realname and nicknames, we can only put an
  45 akill on *Q*@* something which is generally not so great.
  46
  47 Now lets see what they have in common, they all start with teh letter Q and
  48 have a total of 8 characters, all upcase. Now if we could just add an akill
  49 as this:
  50 *Q{7,CU}*@*
  51
  52 This would mean, akill all idents starting with a capital Q, and 7
  53 characters (7,C) after that and all UPPERCASE (U). Now i'm no real wizard
  54 with making new wildcards and stuff but i'm sure people have already made
  55 up things like this for other programming languages. With this method you
  56 could remove the bots you normally can't.
  57
  58 Another example
  59
  60 bots connect with the ident 1234567_, 6364356_, 9589435_ once again all
  61 random nickname and random nicknames and hosts.
  62
  63 New wakill way of banning this:
  64 *{7,N(0-9)}_@*
  65
  66 Akill all hosts with numbers which have 7 Numeric characters in a row from
  67 the number 0 till 9. and a _ behind it.
  68
  69 These are ways that imho won't kill massive amounts of users like you would
  70 normally with for instance *~Q*@*, if the ident isn't resolved at these
  71 hosts adding a ~ at the beginning makes the chances of a real user having
  72 that exact mask near to 0%, chances of a user having an ident like
  73 ~<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">84235664_ at host.here</A> is very small, however banning a host like this with
  74 *~{7,N(0-9)}_@* would remove all the bots you had that were for instance
  75 flooding.
  76
  77 The reason i call it WAKILL, is because it differs so much from real
  78 akills, i just figured WAKILL could mean something like Wildcard Akill.
  79
  80 I personally think this would be a real help on banning bots, with the
  81 current way akills work you can never effectively ban a bot that has a mask
  82 like
  83 *&lt;7 random numbers in a row here&gt;@*
  84
  85 with the new way you would just do *{7,N(0-9)}@* and you've gotten rid of
  86 the bots.
  87
  88 This can be combined with Numeric, Characters or Alfa numeric characters of
  89 course, you could set a thing like
  90
  91 *{7,UC(A-F)}@* to for instance ban idents with 7 characters in a row
  92 differing from the letter A till the letter F, all being Uppercase.
  93
  94 I personally really don't feel users would be affected with this way of
  95 akilling but bots would get removed alot faster and easier. If a botnet
  96 with idents like the one i just said connect, with over 500 bots all random
  97 hosts, nicknames and realnames you can't effectively ban them at all. With
  98 this new way you can.
  99
 100 I hope you all get my point.
 101
 102 - CaliMonk
 103
 104 ---------------------------------------
 105 CaliMonk
 106 Network Administrator
 107 Axenet IRC Network
 108 <A HREF="http://www.axenet.org">http://www.axenet.org</A>
 109 ICQ#: 12000049
 110 MSN: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">calimonk at gmx.net</A>
 111 ---------------------------------------
 112
 113
 114
 115 </PRE>
 116
 117 <!--endarticle-->
 118     <HR>
 119     <P><UL>
 120         <!--threads-->
 121         <LI>Previous message: <A HREF="003399.html">[IRCServices] sqline reason not working...
 122 </A></li>
 123         <LI>Next message: <A HREF="003401.html">[IRCServices] My ideas for WAKILL
 124 </A></li>
 125          <LI> <B>Messages sorted by:</B>
 126               <a href="date.html#3400">[ date ]</a>
 127               <a href="thread.html#3400">[ thread ]</a>
 128               <a href="subject.html#3400">[ subject ]</a>
 129               <a href="author.html#3400">[ author ]</a>
 130          </LI>
 131        </UL>
 132
 133 </body></html>