1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] RE: my recent feature request
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20RE%3A%20my%20recent%20feature%20request&In-Reply-To=41E4C2E5.5040101%40earthlink.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=
"004757.html">
11 <LINK REL=
"Next" HREF=
"004753.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] RE: my recent feature request
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20RE%3A%20my%20recent%20feature%20request&In-Reply-To=41E4C2E5.5040101%40earthlink.net"
17 TITLE=
"[IRCServices] RE: my recent feature request">Craig at frostycoolslug.com
19 <I>Wed Jan
12 11:
10:
21 PST
2005</I>
21 <LI>Previous message:
<A HREF=
"004757.html">[IRCServices] RE: my recent feature request
23 <LI>Next message:
<A HREF=
"004753.html">[IRCServices] RE: my recent feature request
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#4749">[ date ]
</a>
27 <a href=
"thread.html#4749">[ thread ]
</a>
28 <a href=
"subject.html#4749">[ subject ]
</a>
29 <a href=
"author.html#4749">[ author ]
</a>
34 <PRE>aah, my mistake, i dont see any problem with this then :)
36 /****************************************
37 * Craig
"FrostyCoolSlug
" McLure
38 *
<A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">Craig at FrostyCoolSlug.com
</A>
39 * InspIRCd -
<A HREF=
"http://www.inspircd.org">http://www.inspircd.org
</A>
40 * ChatSpike -
<A HREF=
"http://www.chatspike.net">http://www.chatspike.net
</A>
41 ****************************************/
43 <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">youph at earthlink.net
</A> wrote:
44 ><i> Craig McLure wrote:
46 </I>>><i> heh, i think we are all still recovering from christmas, i've not seen
47 </I>>><i> many posts here over that season.
49 </I>>><i> I personally (and i think andy would have the same responce, i've
50 </I>>><i> gotten to know him over the past few years), would shoot down this
51 </I>>><i> idea, it has quite a large potential to be abused, if you write a
52 </I>>><i> patch, ensure only specific IPs can issue the command, otherwise you
53 </I>>><i> will have users just making scripts which periodicly register nicks,
54 </I>>><i> and you'll only become suspicious when your nick.db is
3gigs big :p
56 </I>>><i> My approach would be a seperate module, which deals with the command,
57 </I>>><i> whether its an 'extention' to nickserv with a new command, or a
58 </I>>><i> completly new service which manages it (The second is the method we
59 </I>>><i> used for our web interface), that way, you could also publish your
60 </I>>><i> work, and give the others the benifit of your experiance (but ofc,
61 </I>>><i> thats up to you).
63 </I>>><i> As for a feature request 'process', just post ideas to the list, they
64 </I>>><i> will be read over, if not responded too.
66 </I>>><i> /****************************************
67 </I>>><i> * Craig
"FrostyCoolSlug
" McLure
68 </I>>><i> *
<A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">Craig at FrostyCoolSlug.com
</A>
69 </I>>><i> * InspIRCd -
<A HREF=
"http://www.inspircd.org">http://www.inspircd.org
</A>
70 </I>>><i> * ChatSpike -
<A HREF=
"http://www.chatspike.net">http://www.chatspike.net
</A>
71 </I>>><i> ****************************************/
73 </I>>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">youph at earthlink.net
</A> wrote:
75 </I>>>><i> I'm just wondering if there is any 'official' feature request process
76 </I>>>><i> or if Andrew Church just takes what he likes from this list into
77 </I>>>><i> account when adding new features. I do appreciate Anton Wolkov's
78 </I>>>><i> input, but I was hoping for a response from the developer at least
79 </I>>>><i> either agreeing with or shooting down my idea/request.
81 </I>>>><i> Maybe I should roll up my sleeves and write a patch myself (sigh.)
83 </I>>>><i> --Matt
84 </I>>>><i> ------------------------------------------------------------------
85 </I>>>><i> To unsubscribe or change your subscription options, visit:
86 </I>>>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices
</A>
88 </I>>><i> ------------------------------------------------------------------
89 </I>>><i> To unsubscribe or change your subscription options, visit:
90 </I>>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices
</A>
94 </I>><i> I think you have the wrong idea concerning how I would implement the
95 </I>><i> feature I requested. Let me rephrase my idea/request.
97 </I>><i> I would like the ability for Services Admins to be able to set a user
98 </I>><i> password using an MD5 hash, when using MD5 encrypted passwords with
99 </I>><i> services. Normally, a user registers a nick and provides a plaintext
100 </I>><i> password. This plaintext pass is then hashed and stored in the db (if
101 </I>><i> encryption is enabled which I am saying is true in this instance.) I
102 </I>><i> would like the ability for Services Admins to be able to *directly* set
103 </I>><i> this parameter in a nick record. I.E. I would like to be able to change
104 </I>><i> the *hashed* passwords of users. The only command for dealing with MD5
105 </I>><i> passwords is resetting. It would seem trivial to add the ability to
106 </I>><i> simply overwrite the MD5 hash parameter in the nick record. The reason
107 </I>><i> being I am trying to automate a registration process that starts with a
108 </I>><i> web forum registration and will (hopefully) also register a nick name on
109 </I>><i> IRC for the user. I would only have the MD5 hash of the user's password
110 </I>><i> though, which leads me to this request.
112 </I>><i> I don't see *any* abuse potential as this command extension would be
113 </I>><i> restricted to Service Admins, I think you just were confused by my
114 </I>><i> description.
118 </I>><i> ------------------------------------------------------------------
119 </I>><i> To unsubscribe or change your subscription options, visit:
120 </I>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices
</A>
135 <LI>Previous message:
<A HREF=
"004757.html">[IRCServices] RE: my recent feature request
137 <LI>Next message:
<A HREF=
"004753.html">[IRCServices] RE: my recent feature request
139 <LI> <B>Messages sorted by:
</B>
140 <a href=
"date.html#4749">[ date ]
</a>
141 <a href=
"thread.html#4749">[ thread ]
</a>
142 <a href=
"subject.html#4749">[ subject ]
</a>
143 <a href=
"author.html#4749">[ author ]
</a>
projects / irc.git / blob