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