software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2004/004221.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] secure Identify Feature..
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20secure%20Identify%20Feature..&In-Reply-To=407c7a68.52474%40mail.achurch.org">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="004231.html">
  11    <LINK REL="Next"  HREF="004225.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] secure Identify Feature..</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20secure%20Identify%20Feature..&In-Reply-To=407c7a68.52474%40mail.achurch.org"
  17        TITLE="[IRCServices] secure Identify Feature..">achurch at achurch.org
  18        </A><BR>
  19     <I>Wed Apr 14 09:42:30 PDT 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="004231.html">[IRCServices] secure Identify Feature..
  22 </A></li>
  23         <LI>Next message: <A HREF="004225.html">[IRCServices] Services 5.0.30 released
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#4221">[ date ]</a>
  27               <a href="thread.html#4221">[ thread ]</a>
  28               <a href="subject.html#4221">[ subject ]</a>
  29               <a href="author.html#4221">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i>Another possible advantage to this command thou.. If for some weird
  35 </I>&gt;<i>reason, someone finds your channel password, this command would prevent
  36 </I>&gt;<i>them from doing anything with it, as they would not be able to log on as
  37 </I>&gt;<i>channel founder (Unless they were on the access list).
  38 </I>
  39      It's always been my policy not to try and defend against user
  40 stupidity; &quot;build idiot-proof software, and Nature will build a better
  41 idiot&quot;--it's a losing battle.  I realize that with the glut of online
  42 services these days, it's next to impossible to memorize &quot;good&quot;, distinct
  43 passwords for everything, and I'll admit even I keep my less important
  44 passwords stored in an encrypted file on my PC.  Nonetheless, the password
  45 itself should almost never be needed, since the founder can perform all
  46 founder functions (except dropping) by identifying for their nick.  If the
  47 founder does choose to share the password, e.g. while going on vacation,
  48 and said password is abused, as far as I'm concerned that's their fault,
  49 and there's nothing Services should do about it.
  50
  51   --Andrew Church
  52     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
  53     <A HREF="http://achurch.org/">http://achurch.org/</A>
  54
  55
  56 </PRE>
  57
  58 <!--endarticle-->
  59     <HR>
  60     <P><UL>
  61         <!--threads-->
  62         <LI>Previous message: <A HREF="004231.html">[IRCServices] secure Identify Feature..
  63 </A></li>
  64         <LI>Next message: <A HREF="004225.html">[IRCServices] Services 5.0.30 released
  65 </A></li>
  66          <LI> <B>Messages sorted by:</B>
  67               <a href="date.html#4221">[ date ]</a>
  68               <a href="thread.html#4221">[ thread ]</a>
  69               <a href="subject.html#4221">[ subject ]</a>
  70               <a href="author.html#4221">[ author ]</a>
  71          </LI>
  72        </UL>
  73
  74 </body></html>