software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2005/004756.html

   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=43226.62.231.155.3.1105529514.squirrel%4062.231.155.3">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="004748.html">
  11    <LINK REL="Next"  HREF="004757.html">
  12  </HEAD>
  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=43226.62.231.155.3.1105529514.squirrel%4062.231.155.3"
  17        TITLE="[IRCServices] RE: my recent feature request">youph at earthlink.net
  18        </A><BR>
  19     <I>Thu Jan 13 01:08:55 PST 2005</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="004748.html">[IRCServices] RE: my recent feature request
  22 </A></li>
  23         <LI>Next message: <A HREF="004757.html">[IRCServices] RE: my recent feature request
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#4756">[ date ]</a>
  27               <a href="thread.html#4756">[ thread ]</a>
  28               <a href="subject.html#4756">[ subject ]</a>
  29               <a href="author.html#4756">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Chris Jenkinson wrote:
  35
  36 &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:
  37 </I>&gt;<i>
  38 </I>&gt;<i>
  39 </I>&gt;&gt;<i>I would like the ability for Services Admins to be able to set a user
  40 </I>&gt;&gt;<i>password using an MD5 hash, when using MD5 encrypted passwords with
  41 </I>&gt;&gt;<i>services. Normally, a user registers a nick and provides a plaintext
  42 </I>&gt;&gt;<i>password. This plaintext pass is then hashed and stored in the db (if
  43 </I>&gt;&gt;<i>encryption is enabled which I am saying is true in this instance.) I
  44 </I>&gt;&gt;<i>would like the ability for Services Admins to be able to *directly* set
  45 </I>&gt;&gt;<i>this parameter in a nick record. I.E. I would like to be able to change
  46 </I>&gt;&gt;<i>the *hashed* passwords of users. The only command for dealing with MD5
  47 </I>&gt;&gt;<i>passwords is resetting. It would seem trivial to add the ability to
  48 </I>&gt;&gt;<i>simply overwrite the MD5 hash parameter in the nick record. The reason
  49 </I>&gt;&gt;<i>being I am trying to automate a registration process that starts with a
  50 </I>&gt;&gt;<i>web forum registration and will (hopefully) also register a nick name on
  51 </I>&gt;&gt;<i>IRC for the user. I would only have the MD5 hash of the user's password
  52 </I>&gt;&gt;<i>though, which leads me to this request.
  53 </I>&gt;&gt;<i>
  54 </I>&gt;&gt;<i>
  55 </I>&gt;<i>
  56 </I>&gt;<i>Kind of off-topic here and out of curiousity, how do you aim to handle a
  57 </I>&gt;<i>situation where someone registers an account on your website which isn't
  58 </I>&gt;<i>usable as an IRC nick (for example &quot;Hello Bob&quot;)? I've been considering a
  59 </I>&gt;<i>problem like this for some time and I'd like to see how someone else is
  60 </I>&gt;<i>aiming to do it.
  61 </I>&gt;<i>
  62 </I>&gt;<i>Chris
  63 </I>&gt;<i>
  64 </I>&gt;<i>
  65 </I>&gt;<i>
  66 </I>Chris,
  67
  68 I realized my response to your question was incomplete so let me expound
  69 further.
  70
  71 The general idea for validating a user name from our bulletin board
  72 software would be something like this:
  73 a) check length against max nick length and shorten as required
  74 b) search for incompatible characters such as * or @ in the user name
  75 and simply remove
  76 c) check for space in the user name and replace them with and underscore
  77 character _
  78 d) remember this nick (if it differs from the user name for the forums)
  79 and email the nick with instructions on how to connect to IRC to the new
  80 user
  81 I may have forgot some details but it&#8217;s totally doable.
  82
  83 </PRE>
  84
  85
  86 <!--endarticle-->
  87     <HR>
  88     <P><UL>
  89         <!--threads-->
  90         <LI>Previous message: <A HREF="004748.html">[IRCServices] RE: my recent feature request
  91 </A></li>
  92         <LI>Next message: <A HREF="004757.html">[IRCServices] RE: my recent feature request
  93 </A></li>
  94          <LI> <B>Messages sorted by:</B>
  95               <a href="date.html#4756">[ date ]</a>
  96               <a href="thread.html#4756">[ thread ]</a>
  97               <a href="subject.html#4756">[ subject ]</a>
  98               <a href="author.html#4756">[ author ]</a>
  99          </LI>
 100        </UL>
 101
 102 </body></html>