]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001492.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 001492.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] Some IMHO usefull features
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Some%20IMHO%20usefull%20features&In-Reply-To=F61aCxyst1130OBFbCU000021bb%40hotmail.com">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001491.html">
11 <LINK REL="Next" HREF="001496.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] Some IMHO usefull features</H1>
15 <B>Ekim Engin</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Some%20IMHO%20usefull%20features&In-Reply-To=F61aCxyst1130OBFbCU000021bb%40hotmail.com"
17 TITLE="[IRCServices Coding] Some IMHO usefull features">ekim.engin at stud.uni-karlsruhe.de
18 </A><BR>
19 <I>Sat Sep 21 19:53:03 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001491.html">[IRCServices Coding] Some IMHO usefull features
22 </A></li>
23 <LI>Next message: <A HREF="001496.html">AW: [IRCServices Coding] Some IMHO usefull features
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1492">[ date ]</a>
27 <a href="thread.html#1492">[ thread ]</a>
28 <a href="subject.html#1492">[ subject ]</a>
29 <a href="author.html#1492">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i> 1, Personally, I dont see the point in this. If you ban an
35 </I>&gt;<i> email block, they
36 </I>&gt;<i> will just find another 1. for example, you cant ban
37 </I>&gt;<i> *.hotmail.com on a
38 </I>&gt;<i> network, so the &quot;stupid kiddies&quot; will just use something like
39 </I>&gt;<i> that. Just
40 </I>&gt;<i> insert a largish reg delay, it would mean they would have to
41 </I>&gt;<i> change their
42 </I>&gt;<i> IP, or wait for something like 60mins before being able to
43 </I>&gt;<i> register again.
44 </I>&gt;<i>
45 </I>
46 Huge proxy atacks, or even more DDOS atacks registering 1 nick per hour
47 with 500 hosts is quite disturbing. Services is sending out many mails
48 (to adresses that do not exist) and we get the bounces. I implemented
49 this feature on an earlier version of ircservices with the result, that
50 the complete &quot;registration atack&quot; stopped. I reopend the ban 2 days
51 after, and the atack continued on same speed. Ist is based on a one time
52 initialisation, spreadign out through a common used but backdoored
53 script. Once started it does the registering crap all the time. Akilling
54 (or glineing) just results in the user getting banned. After he/she
55 comes back, the script continues registering. The only thing common to
56 this atacks is it uses alwas the same mail adresses. So I thought this
57 as quite usefull, it's just a suggestion after all.
58
59 &gt;<i> 2) Once again, i dont see a point for this feature. It would
60 </I>&gt;<i> make channels
61 </I>&gt;<i> prone to opwars, and takeovers. although the SUSPEND command
62 </I>&gt;<i> does do what
63 </I>&gt;<i> you ask, but i am unsure if it supports wildcards.
64 </I>
65 Suspend does prevent registering AND using of the channel, while my
66 feature suggestion just prevents registering. We came up with this
67 feature afer every single channel gets registerd with #ttnet_channelname
68 (the network is called TTNet). As it is our Network policy that channels
69 starting with #ttnet may just be registerd by our network stuff, it is
70 quite annoying to stop/drop/suspend these channels all the time, while
71 with this feature does allow us to prevent this from scratch.
72
73 &gt;<i>
74 </I>&gt;<i> --
75 </I>&gt;<i> Craig McLure
76 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">Craig at chatspike.net</A>
77 </I>&gt;<i> Network Administrator of the ChatSpike IRC Network.
78 </I>&gt;<i> ChatSpike, the users network! www.chatspike.net
79 </I>&gt;<i>
80 </I>&gt;<i> The InspIRCd Project, The Next Generation in IRCds.. Alpha0
81 </I>&gt;<i> Avaliable today!
82 </I>&gt;<i> <A HREF="http://www.sourceforge.net/projects/inspircd">http://www.sourceforge.net/projects/inspircd</A>
83 </I>&gt;<i>
84 </I>&gt;<i> _________________________________________________________________
85 </I>&gt;<i> Send and receive Hotmail on your mobile device: <A HREF="http://mobile.msn.com">http://mobile.msn.com</A>
86 </I>&gt;<i>
87 </I>&gt;<i> ------------------------------------------------------------------
88 </I>&gt;<i> To unsubscribe or change your subscription options, visit:
89 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo">http://www.ircservices.za.net/mailman/listinfo</A>&gt; /ircservices-coding
90 </I>&gt;<i>
91 </I>&gt;<i>
92 </I>
93 +------------------------+------------------------+
94 |<i> Talesin aka Ekim Engin | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">talesin at tr-ircd.net</A> |
95 </I>|<i> TR-IRCd Coding Team | <A HREF="http://www.tr-ircd.net">http://www.tr-ircd.net</A> |
96 </I>|<i>------------------------^------------------------|
97 </I>|<i> It's time to go five - Join the revolution |
98 </I>+-------------------------------------------------+
99
100
101 </PRE>
102
103 <!--endarticle-->
104 <HR>
105 <P><UL>
106 <!--threads-->
107 <LI>Previous message: <A HREF="001491.html">[IRCServices Coding] Some IMHO usefull features
108 </A></li>
109 <LI>Next message: <A HREF="001496.html">AW: [IRCServices Coding] Some IMHO usefull features
110 </A></li>
111 <LI> <B>Messages sorted by:</B>
112 <a href="date.html#1492">[ date ]</a>
113 <a href="thread.html#1492">[ thread ]</a>
114 <a href="subject.html#1492">[ subject ]</a>
115 <a href="author.html#1492">[ author ]</a>
116 </LI>
117 </UL>
118
119 </body></html>