software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2004/004220.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=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="004219.html">
  11    <LINK REL="Next"  HREF="004222.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] secure Identify Feature..</H1>
  15     <B>Craig McLure</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20secure%20Identify%20Feature..&In-Reply-To="
  17        TITLE="[IRCServices] secure Identify Feature..">Craig at chatspike.net
  18        </A><BR>
  19     <I>Tue Apr 13 17:39:43 PDT 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="004219.html">[IRCServices] secure Identify Feature..
  22 </A></li>
  23         <LI>Next message: <A HREF="004222.html">[IRCServices] secure Identify Feature..
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#4220">[ date ]</a>
  27               <a href="thread.html#4220">[ thread ]</a>
  28               <a href="subject.html#4220">[ subject ]</a>
  29               <a href="author.html#4220">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>I read this mail, and read it again, and its absolutly right, with some careful manipulation of the /cs levels command, along with /cs access, you can basically give people 'Founder' privs without them being founder. Another possible advantage to this command thou.. If for some weird reason, someone finds your channel password, this command would prevent them from doing anything with it, as they would not be able to log on as channel founder (Unless they were on the access list). sometimes the distributation of channel passwords may be present when the real founder cant get at the channel for various reasons, and they give the password to the successor, or someone else trustworthy. From where i'm sitting, I cant really see any other real use for this function.
  35
  36 /****************************************
  37  *     Craig &quot;FrostyCoolSlug&quot; McLure
  38  * InspIRCd   - <A HREF="http://www.inspircd.org">http://www.inspircd.org</A>  - REVIVED
  39  * ChatSpike  - <A HREF="http://www.chatspike.net">http://www.chatspike.net</A>
  40  ****************************************/
  41
  42
  43 /****************************************
  44  * From    - M &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net</A>&gt;
  45  * To      - 'IRC Services General Mailing List' &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>&gt;
  46  * Sent    - 2004-04-13 23:08:45
  47  * Subject - RE: RE: [IRCServices] secure Identify Feature..
  48  ****************************************/
  49
  50 /****** - Begin Original Message - ******/
  51
  52 &gt;<i>Craig McLure wrote:
  53 </I>&gt;&gt;<i> This command would add things to make the channel more secure
  54 </I>&gt;&gt;<i> thou, If you did give the channel founder password to people
  55 </I>&gt;&gt;<i> you trust, and you find its being abused, you can simply
  56 </I>&gt;&gt;<i> remove that person from the access list, this way you dont
  57 </I>&gt;&gt;<i> need to worry about changing the password and re-distributing it :)
  58 </I>&gt;<i>
  59 </I>&gt;<i>The way to be secure is not to give out the founder password. You could
  60 </I>&gt;<i>apply the same short sighted reason for a &quot;/ns set
  61 </I>&gt;<i>letotherpeopleaccessmynick pass&quot; request.
  62 </I>&gt;<i>
  63 </I>&gt;<i>The founder password is designed to give the channel founder access to
  64 </I>&gt;<i>manage the ownership of the channel. There is no need to give out the
  65 </I>&gt;<i>password to anyone, channel management through others is provided via op
  66 </I>&gt;<i>status.
  67 </I>&gt;<i>
  68 </I>&gt;<i>If for some peculiar reason a channel founder wishes to share the password
  69 </I>&gt;<i>then IMO that is their problem. The chances are that any user that would
  70 </I>&gt;<i>require modifying the access list to &quot;fix&quot; this, would likely be attempted
  71 </I>&gt;<i>too late since a rogue user could have merely taken ownership of the channel
  72 </I>&gt;<i>thereby making the option and the founder password redundant and merely make
  73 </I>&gt;<i>it a problem that administrators waste time on.
  74 </I>&gt;<i>
  75 </I>&gt;<i>The founder can already provide access to whatever commands an op needs via
  76 </I>&gt;<i>levels which is far more secure and already subject to access list
  77 </I>&gt;<i>restrictions.
  78 </I>&gt;<i>
  79 </I>&gt;<i>What function of founder status is required that warrants removing the
  80 </I>&gt;<i>founder status by supporting sharing of it?
  81 </I>&gt;<i>
  82 </I>&gt;<i>M.
  83 </I>&gt;<i>
  84 </I>&gt;<i>
  85 </I>&gt;<i>------------------------------------------------------------------
  86 </I>&gt;<i>To unsubscribe or change your subscription options, visit:
  87 </I>&gt;<i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
  88 </I>&gt;<i>.
  89 </I>
  90 /******* - End Original Message - *******/
  91
  92
  93
  94
  95 </PRE>
  96
  97 <!--endarticle-->
  98     <HR>
  99     <P><UL>
 100         <!--threads-->
 101         <LI>Previous message: <A HREF="004219.html">[IRCServices] secure Identify Feature..
 102 </A></li>
 103         <LI>Next message: <A HREF="004222.html">[IRCServices] secure Identify Feature..
 104 </A></li>
 105          <LI> <B>Messages sorted by:</B>
 106               <a href="date.html#4220">[ date ]</a>
 107               <a href="thread.html#4220">[ thread ]</a>
 108               <a href="subject.html#4220">[ subject ]</a>
 109               <a href="author.html#4220">[ author ]</a>
 110          </LI>
 111        </UL>
 112
 113 </body></html>