software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001633.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Suggestion
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001632.html">
  11    <LINK REL="Next"  HREF="001638.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Suggestion</H1>
  15     <B>Georges Berscheid</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To="
  17        TITLE="[IRCServices] Suggestion">Georges at berscheid.lu
  18        </A><BR>
  19     <I>Mon Mar 19 00:23:01 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001632.html">[IRCServices] Suggestion
  22 </A></li>
  23         <LI>Next message: <A HREF="001638.html">[IRCServices] Suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1633">[ date ]</a>
  27               <a href="thread.html#1633">[ thread ]</a>
  28               <a href="subject.html#1633">[ subject ]</a>
  29               <a href="author.html#1633">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Hi,
  35
  36 &gt;<i> Each time a nickname is registered, a nick gets an authentication code, a
  37 </I>&gt;<i> la dalnet, which cannot be changed, and which is not shown. Thi code is
  38 </I>&gt;<i> emailed to the address given with the register command.  After that, the
  39 </I>&gt;<i> person has to issue /nickserv AUTH &lt;code&gt; within some services.conf days,
  40 </I>&gt;<i> or the registration will expire. If people claim to have lost their
  41 </I>&gt;<i> passwords, but can prove that they have the authentication code, because
  42 </I>&gt;<i> it was emailed to them, a services oper can issue /nickserv GETAUTH nick,
  43 </I>&gt;<i> and check the real authentication code against the given, if they match,
  44 </I>&gt;<i> it is highly possible that the person is the real owner, so
  45 </I>&gt;<i> sendpass/getpass can be issued.
  46 </I>
  47 Why don't you just email the password to them when they register, so they
  48 can look it up if they forget it. If they lose the EMail as well, they will
  49 lose the AUTH EMail too. So your (in my eyes, quite complicated system of 2
  50 passwords) becomes obsolete.
  51 I don't really see the use of this system. You can do whatever you want, but
  52 you'll never be able to eliminate the stupidness of the users ;-)
  53 You could even force passwords to contain numbers or special chars if you
  54 want a higher security level.
  55
  56 Greetings
  57
  58 Georges
  59
  60
  61
  62 </PRE>
  63
  64 <!--endarticle-->
  65     <HR>
  66     <P><UL>
  67         <!--threads-->
  68         <LI>Previous message: <A HREF="001632.html">[IRCServices] Suggestion
  69 </A></li>
  70         <LI>Next message: <A HREF="001638.html">[IRCServices] Suggestion
  71 </A></li>
  72          <LI> <B>Messages sorted by:</B>
  73               <a href="date.html#1633">[ date ]</a>
  74               <a href="thread.html#1633">[ thread ]</a>
  75               <a href="subject.html#1633">[ subject ]</a>
  76               <a href="author.html#1633">[ author ]</a>
  77          </LI>
  78        </UL>
  79
  80 </body></html>