1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] My ideas for WAKILL
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=11BBDE9A-0DBC-11D7-BA88-0003938D6866%40softhome.net">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"003401.html">
11 <LINK REL=
"Next" HREF=
"003404.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] My ideas for WAKILL
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20My%20ideas%20for%20WAKILL&In-Reply-To=11BBDE9A-0DBC-11D7-BA88-0003938D6866%40softhome.net"
17 TITLE=
"[IRCServices] My ideas for WAKILL">calimonk at gmx.net
19 <I>Thu Dec
12 12:
39:
00 PST
2002</I>
21 <LI>Previous message:
<A HREF=
"003401.html">[IRCServices] My ideas for WAKILL
23 <LI>Next message:
<A HREF=
"003404.html">[IRCServices] My ideas for WAKILL
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#3402">[ date ]
</a>
27 <a href=
"thread.html#3402">[ thread ]
</a>
28 <a href=
"subject.html#3402">[ subject ]
</a>
29 <a href=
"author.html#3402">[ author ]
</a>
34 <PRE>At
02:
25 12-
12-
2002 -
0800, you wrote:
35 ><i>On Thursday, Dec
12,
2002, at
01:
09 US/Pacific, calimonk wrote:
37 </I>><i>Just a couple quick comments:
39 Thanks, comments are always good :P
42 >><i><snip
>
44 </I>><i>The problem is, you still can't ban them. Why not? Lack of server
45 </I>><i>support. As far as I know, none of the supported ircds support
46 </I>><i>regex or similar akills. If ircservices itself implemented this,
47 </I>><i>you'd just get a burst of kills, and no bans.
49 I never really thought of it IRCd wise to be honest, the idea just came to
50 my head and i just had to share. I get your point though.
52 ><i>It also needs to be 'standardized'. You really DON'T want to use
53 </I>><i>full regex on IRC -- way too much abuse potential. But getting
54 </I>><i>everyone to agree on a supported subset? Good luck. People have
55 </I>><i>been trying to sneak regex-type solutions into ircds for years.
56 </I>><i>So far I haven't seen anything stick.
58 </I>><i>And as far as the random bot nicks go, even regex is largely
59 </I>><i>inadequate. One solution I've seen recently is in bahamut
1.4.35
60 </I>><i>-- support for a loadable 'drone' module. While the module
61 </I>><i>itself is unavailable to the public, its concept is simple. It
62 </I>><i>gets hooked when a user connects, and fed all the info (nick,
63 </I>><i>ident, host, realname). That module can do whatever processing
64 </I>><i>it wants to determine whether a client is valid or not.
66 </I>><i>Consider, for example, the actual from-the-wild nick GVTiqflB.
67 </I>><i>Suppose its generator simply grabs a random alphabetic character.
68 </I>><i>How on earth are you going to describe any useful ban on that
69 </I>><i>nick, be it with regex or another method?
71 </I>><i>An arbitrary processor such as the 'drone module' I mentioned
72 </I>><i>above can do something like upper/lower case character
73 </I>><i>probability analysis (in english: look for mixed-case junk).
74 </I>><i>Regular Expressions can't do that.
76 The thing with the bots is that they almost always have a
"~
" adding this
77 to a 'regular expression akill' would not affect alot of users if it would
79 If it can't be done by akills, because of the ircd then perhaps some sort
80 of module for ircservices. One that does something like the 'drone'
83 The thing only is, if you can't
"Ban
" people from a server with the
84 'regular expressions' then you have to face the fact that you will have to
85 add MASSIVE amounts of seperate akills set by for instance a drone monitor
86 in stead of the '
1' regular expression akill.
88 ><i>Getting back to your original idea, I do agree that such a
89 </I>><i>"string description syntax
" (seems as good a term as any ;) )
90 </I>><i>would be very useful. I'm just commenting on some of the
91 </I>><i>problems involved in creating it.
93 </I>><i>-- Quension
95 As always any idea i seem to come up with always has a few problems with it
96 in creating. I've been looking for ways of removing flooding bots and the
97 like for quite some time, and the fact just remains that with teh currently
98 akill way you in no way can get rid of them.
100 Maybe i shouldn't have send this email to ircservices mailing list but to
101 for instance an IRCd mailing list. Like for instance a new sort of command
102 alternative to gline. Like you said alot of 'security' risks are connected
105 I just feel that there has to be a way to stop all these bots from
106 attacking, and regular akills/glines and the like just don't stand anymore.
108 ><i>------------------------------------------------------------------
109 </I>><i>To unsubscribe or change your subscription options, visit:
110 </I>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
112 ---------------------------------------
114 Network Administrator
116 <A HREF=
"http://www.axenet.org">http://www.axenet.org
</A>
118 MSN:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">calimonk at gmx.net
</A>
119 ---------------------------------------
129 <LI>Previous message:
<A HREF=
"003401.html">[IRCServices] My ideas for WAKILL
131 <LI>Next message:
<A HREF=
"003404.html">[IRCServices] My ideas for WAKILL
133 <LI> <B>Messages sorted by:
</B>
134 <a href=
"date.html#3402">[ date ]
</a>
135 <a href=
"thread.html#3402">[ thread ]
</a>
136 <a href=
"subject.html#3402">[ subject ]
</a>
137 <a href=
"author.html#3402">[ author ]
</a>
projects / irc.git / blob