[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2005 / 004757.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices] RE: my recent feature request
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20RE%3A%20my%20recent%20feature%20request&In-Reply-To=41E63AA7.3090000%40earthlink.net">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="004756.html">
   <LINK REL="Next"  HREF="004749.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices] RE: my recent feature request</H1>
    <B>Craig Edwards</B> 
    <A HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20RE%3A%20my%20recent%20feature%20request&In-Reply-To=41E63AA7.3090000%40earthlink.net"
       TITLE="[IRCServices] RE: my recent feature request">brain at winbot.co.uk
       </A><BR>
    <I>Thu Jan 13 13:06:28 PST 2005</I>
    <P><UL>
        <LI>Previous message: <A HREF="004756.html">[IRCServices] RE: my recent feature request
</A></li>
        <LI>Next message: <A HREF="004749.html">[IRCServices] RE: my recent feature request
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#4757">[ date ]</a>
              <a href="thread.html#4757">[ thread ]</a>
              <a href="subject.html#4757">[ subject ]</a>
              <a href="author.html#4757">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If you read RFC 1459 there is a BNF specification for a nickname, it's
actually a pretty small number of valid characters, also you cant start
a nick with a number, or with a -, but these can follow on in the nickname.

Also BE VERY CAREFUL to check for forbidden nicknames etc, you can
segfault services if you try and do things with a forbidden or suspended
nickname.

<A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">youph at earthlink.net</A> wrote:
|<i> Chris Jenkinson wrote:
</I>|<i>
</I>|&gt;<i> On Wed, January 12, 2005 6:25 am, <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">youph at earthlink.net</A> said:
</I>|&gt;<i>
</I>|&gt;<i>
</I>|&gt;&gt;<i> I would like the ability for Services Admins to be able to set a user
</I>|&gt;&gt;<i> password using an MD5 hash, when using MD5 encrypted passwords with
</I>|&gt;&gt;<i> services. Normally, a user registers a nick and provides a plaintext
</I>|&gt;&gt;<i> password. This plaintext pass is then hashed and stored in the db (if
</I>|&gt;&gt;<i> encryption is enabled which I am saying is true in this instance.) I
</I>|&gt;&gt;<i> would like the ability for Services Admins to be able to *directly* set
</I>|&gt;&gt;<i> this parameter in a nick record. I.E. I would like to be able to change
</I>|&gt;&gt;<i> the *hashed* passwords of users. The only command for dealing with MD5
</I>|&gt;&gt;<i> passwords is resetting. It would seem trivial to add the ability to
</I>|&gt;&gt;<i> simply overwrite the MD5 hash parameter in the nick record. The reason
</I>|&gt;&gt;<i> being I am trying to automate a registration process that starts with a
</I>|&gt;&gt;<i> web forum registration and will (hopefully) also register a nick name on
</I>|&gt;&gt;<i> IRC for the user. I would only have the MD5 hash of the user's password
</I>|&gt;&gt;<i> though, which leads me to this request.
</I>|&gt;&gt;<i>
</I>|&gt;<i>
</I>|&gt;<i>
</I>|&gt;<i> Kind of off-topic here and out of curiousity, how do you aim to handle a
</I>|&gt;<i> situation where someone registers an account on your website which isn't
</I>|&gt;<i> usable as an IRC nick (for example &quot;Hello Bob&quot;)? I've been considering a
</I>|&gt;<i> problem like this for some time and I'd like to see how someone else is
</I>|&gt;<i> aiming to do it.
</I>|&gt;<i>
</I>|&gt;<i> Chris
</I>|&gt;<i>
</I>|&gt;<i>
</I>|&gt;<i>
</I>|<i> Chris,
</I>|<i>
</I>|<i> I realized my response to your question was incomplete so let me expound
</I>|<i> further.
</I>|<i>
</I>|<i> The general idea for validating a user name from our bulletin board
</I>|<i> software would be something like this:
</I>|<i> a) check length against max nick length and shorten as required
</I>|<i> b) search for incompatible characters such as * or @ in the user name
</I>|<i> and simply remove
</I>|<i> c) check for space in the user name and replace them with and underscore
</I>|<i> character _
</I>|<i> d) remember this nick (if it differs from the user name for the forums)
</I>|<i> and email the nick with instructions on how to connect to IRC to the new
</I>|<i> user
</I>|<i> I may have forgot some details but it?s totally doable.
</I>|<i>
</I>|<i> ------------------------------------------------------------------
</I>|<i> To unsubscribe or change your subscription options, visit:
</I>|<i> <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices</A>
</I>|<i>
</I>|<i>
</I>
- --
WinBot IRC client developer: <A HREF="http://www.winbot.co.uk">http://www.winbot.co.uk</A>
ChatSpike - The users network: <A HREF="http://www.chatspike.net">http://www.chatspike.net</A>
InspIRCd - Modular IRC server: <A HREF="http://www.inspircd.org">http://www.inspircd.org</A>
Online RPG Developer: <A HREF="http://www.ssod.org">http://www.ssod.org</A>
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - <A HREF="http://enigmail.mozdev.org">http://enigmail.mozdev.org</A>

iD8DBQFB5uLU0k42Wxli/BARAut2AJ0W1G0gt+9TMPe9ugWTKFsf7fm1FwCfdEvT
RaurRTXx3cuitYxzWi6AHEo=
=l4lm
-----END PGP SIGNATURE-----
</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="004756.html">[IRCServices] RE: my recent feature request
</A></li>
	<LI>Next message: <A HREF="004749.html">[IRCServices] RE: my recent feature request
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#4757">[ date ]</a>
              <a href="thread.html#4757">[ thread ]</a>
              <a href="subject.html#4757">[ subject ]</a>
              <a href="author.html#4757">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices] RE: my recent feature request
	5	</TITLE>
	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=41E63AA7.3090000%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="004756.html">
	11	<LINK REL="Next" HREF="004749.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices] RE: my recent feature request</H1>
	15	<B>Craig Edwards</B>
	16	<A HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20RE%3A%20my%20recent%20feature%20request&In-Reply-To=41E63AA7.3090000%40earthlink.net"
	17	TITLE="[IRCServices] RE: my recent feature request">brain at winbot.co.uk
	18	</A><BR>
	19	<I>Thu Jan 13 13:06:28 PST 2005</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="004756.html">[IRCServices] RE: my recent feature request
	22	</A></li>
	23	<LI>Next message: <A HREF="004749.html">[IRCServices] RE: my recent feature request
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#4757">[ date ]</a>
	27	<a href="thread.html#4757">[ thread ]</a>
	28	<a href="subject.html#4757">[ subject ]</a>
	29	<a href="author.html#4757">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>-----BEGIN PGP SIGNED MESSAGE-----
	35	Hash: SHA1
	36
	37	If you read RFC 1459 there is a BNF specification for a nickname, it's
	38	actually a pretty small number of valid characters, also you cant start
	39	a nick with a number, or with a -, but these can follow on in the nickname.
	40
	41	Also BE VERY CAREFUL to check for forbidden nicknames etc, you can
	42	segfault services if you try and do things with a forbidden or suspended
	43	nickname.
	44
	45	<A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">youph at earthlink.net</A> wrote:
	46	\|<i> Chris Jenkinson wrote:
	47	</I>\|<i>
	48	</I>\|><i> On Wed, January 12, 2005 6:25 am, <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">youph at earthlink.net</A> said:
	49	</I>\|><i>
	50	</I>\|><i>
	51	</I>\|>><i> I would like the ability for Services Admins to be able to set a user
	52	</I>\|>><i> password using an MD5 hash, when using MD5 encrypted passwords with
	53	</I>\|>><i> services. Normally, a user registers a nick and provides a plaintext
	54	</I>\|>><i> password. This plaintext pass is then hashed and stored in the db (if
	55	</I>\|>><i> encryption is enabled which I am saying is true in this instance.) I
	56	</I>\|>><i> would like the ability for Services Admins to be able to directly set
	57	</I>\|>><i> this parameter in a nick record. I.E. I would like to be able to change
	58	</I>\|>><i> the hashed passwords of users. The only command for dealing with MD5
	59	</I>\|>><i> passwords is resetting. It would seem trivial to add the ability to
	60	</I>\|>><i> simply overwrite the MD5 hash parameter in the nick record. The reason
	61	</I>\|>><i> being I am trying to automate a registration process that starts with a
	62	</I>\|>><i> web forum registration and will (hopefully) also register a nick name on
	63	</I>\|>><i> IRC for the user. I would only have the MD5 hash of the user's password
	64	</I>\|>><i> though, which leads me to this request.
65	</I>\|>><i>
66	</I>\|><i>
67	</I>\|><i>
68	</I>\|><i> Kind of off-topic here and out of curiousity, how do you aim to handle a
69	</I>\|><i> situation where someone registers an account on your website which isn't
70	</I>\|><i> usable as an IRC nick (for example "Hello Bob")? I've been considering a
71	</I>\|><i> problem like this for some time and I'd like to see how someone else is
72	</I>\|><i> aiming to do it.
73	</I>\|><i>
74	</I>\|><i> Chris
75	</I>\|><i>
76	</I>\|><i>
77	</I>\|><i>
78	</I>\|<i> Chris,
79	</I>\|<i>
80	</I>\|<i> I realized my response to your question was incomplete so let me expound
81	</I>\|<i> further.
82	</I>\|<i>
83	</I>\|<i> The general idea for validating a user name from our bulletin board
84	</I>\|<i> software would be something like this:
85	</I>\|<i> a) check length against max nick length and shorten as required
86	</I>\|<i> b) search for incompatible characters such as * or @ in the user name
87	</I>\|<i> and simply remove
88	</I>\|<i> c) check for space in the user name and replace them with and underscore
89	</I>\|<i> character _
90	</I>\|<i> d) remember this nick (if it differs from the user name for the forums)
91	</I>\|<i> and email the nick with instructions on how to connect to IRC to the new
92	</I>\|<i> user
93	</I>\|<i> I may have forgot some details but it?s totally doable.
94	</I>\|<i>
95	</I>\|<i> ------------------------------------------------------------------
96	</I>\|<i> To unsubscribe or change your subscription options, visit:
97	</I>\|<i> <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices</A>
98	</I>\|<i>
99	</I>\|<i>
100	</I>
101	- --
102	WinBot IRC client developer: <A HREF="http://www.winbot.co.uk">http://www.winbot.co.uk</A>
103	ChatSpike - The users network: <A HREF="http://www.chatspike.net">http://www.chatspike.net</A>
104	InspIRCd - Modular IRC server: <A HREF="http://www.inspircd.org">http://www.inspircd.org</A>
105	Online RPG Developer: <A HREF="http://www.ssod.org">http://www.ssod.org</A>
106	- --
107	-----BEGIN PGP SIGNATURE-----
108	Version: GnuPG v1.2.5 (MingW32)
109	Comment: Using GnuPG with Thunderbird - <A HREF="http://enigmail.mozdev.org">http://enigmail.mozdev.org</A>
110
111	iD8DBQFB5uLU0k42Wxli/BARAut2AJ0W1G0gt+9TMPe9ugWTKFsf7fm1FwCfdEvT
112	RaurRTXx3cuitYxzWi6AHEo=
113	=l4lm
114	-----END PGP SIGNATURE-----
115	</PRE>
116
117	<!--endarticle-->
118	<HR>
119	<P><UL>
120	<!--threads-->
121	<LI>Previous message: <A HREF="004756.html">[IRCServices] RE: my recent feature request
122	</A></li>
123	<LI>Next message: <A HREF="004749.html">[IRCServices] RE: my recent feature request
124	</A></li>
125	<LI> <B>Messages sorted by:</B>
126	<a href="date.html#4757">[ date ]</a>
127	<a href="thread.html#4757">[ thread ]</a>
128	<a href="subject.html#4757">[ subject ]</a>
129	<a href="author.html#4757">[ author ]</a>
130	</LI>
131	</UL>
132
133	</body></html>