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