software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001629.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="001628.html">
  11    <LINK REL="Next"  HREF="001632.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Suggestion</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To="
  17        TITLE="[IRCServices] Suggestion">achurch at achurch.org
  18        </A><BR>
  19     <I>Sun Mar 18 22:57:01 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001628.html">[IRCServices] A discussion on the contents of the todo file
  22 </A></li>
  23         <LI>Next message: <A HREF="001632.html">[IRCServices] Suggestion
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1629">[ date ]</a>
  27               <a href="thread.html#1629">[ thread ]</a>
  28               <a href="subject.html#1629">[ subject ]</a>
  29               <a href="author.html#1629">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i>I think it would be nice to see a &quot;Last modif by&quot; when useing &quot;/msg
  35 </I>&gt;<i>chanserv access #channel list&quot;.
  36 </I>
  37      I'm not sure of the value of this compared to the amount of
  38 bookkeeping it would take.
  39
  40 &gt;<i>And another thing...this is more a question then a suggestion.
  41 </I>&gt;<i>We have problems with users takeing others nickname password.
  42 </I>&gt;<i>We enforced the use of an email adress when registering a nickname, but
  43 </I>&gt;<i>of course, first thing when somebody take a password is to change that
  44 </I>&gt;<i>address. So we don't have any sure way to check if the new password goes
  45 </I>&gt;<i>to the right address.
  46 </I>&gt;<i>
  47 </I>&gt;<i>And I was thinking...I know it may sound silly...but can we have a
  48 </I>&gt;<i>duplicate db with emails that can be changed just by services admins? Or
  49 </I>&gt;<i>any other way to secure this thing? Ideas? Suggestions? Thanx a lot.
  50 </I>
  51      Since users having their passwords taken almost certainly means they
  52 chose an easy-to-guess password, the right solution is to educate the
  53 users.  I don't see why Services should have to run through hoops to try
  54 and solve this problem.  (Of course, if your server is being
  55 packet-sniffed, then you have other problems altogether.)
  56
  57   --Andrew Church
  58     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | New address - please note.
  59     <A HREF="http://achurch.org/">http://achurch.org/</A> | &#12513;&#12540;&#12523;&#12450;&#12489;&#12524;&#12473;&#12364;&#22793;&#12431;&#12426;&#12414;&#12375;&#12383;&#12290;
  60
  61
  62 </PRE>
  63
  64 <!--endarticle-->
  65     <HR>
  66     <P><UL>
  67         <!--threads-->
  68         <LI>Previous message: <A HREF="001628.html">[IRCServices] A discussion on the contents of the todo file
  69 </A></li>
  70         <LI>Next message: <A HREF="001632.html">[IRCServices] Suggestion
  71 </A></li>
  72          <LI> <B>Messages sorted by:</B>
  73               <a href="date.html#1629">[ date ]</a>
  74               <a href="thread.html#1629">[ thread ]</a>
  75               <a href="subject.html#1629">[ subject ]</a>
  76               <a href="author.html#1629">[ author ]</a>
  77          </LI>
  78        </UL>
  79
  80 </body></html>