software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000499.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Services Admin : Global Access to Channel Settings
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%20Admin%20%3A%20Global%20Access%20to%20Channel%20Settings&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="000498.html">
  11    <LINK REL="Next"  HREF="000503.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Services Admin : Global Access to Channel Settings</H1>
  15     <B>Mark Hetherington</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%20Admin%20%3A%20Global%20Access%20to%20Channel%20Settings&In-Reply-To="
  17        TITLE="[IRCServices Coding] Services Admin : Global Access to Channel Settings">mark at ctcp.net
  18        </A><BR>
  19     <I>Tue Apr  9 16:38:23 PDT 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000498.html">[IRCServices Coding] Services Admin : Global Access to Channel Settings
  22 </A></li>
  23         <LI>Next message: <A HREF="000503.html">[IRCServices Coding] list
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#499">[ date ]</a>
  27               <a href="thread.html#499">[ thread ]</a>
  28               <a href="subject.html#499">[ subject ]</a>
  29               <a href="author.html#499">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Adrian Cantrill wrote:
  35 &gt;<i> A channel takeover situation where a channel founders password is gained
  36 </I>&gt;<i> and the services admin wishes to remove / add channel access to secure
  37 </I>&gt;<i> the situation.
  38 </I>
  39 /msg chanserv suspend #channel
  40 is the easy quick fix. The founder/ops can then fix it themselves at a
  41 later time.
  42
  43 /msg operserv clear #channel ops
  44 would remove everybody with current ops requiring them to re request ops
  45 from ChanServ or hop providing time to do whatever you feel you need to, to
  46 rectify the situation.
  47
  48 /msg chanserv set #channel password newpassword
  49 would fix the problem of a compromised password. This should obviously be
  50 followed by pointing out the need for a decent password to the founder if
  51 this is a common problem on your network.
  52
  53 There are various other commands which could be used, none of which require
  54 comprimising the founder's right to manage their own access list.
  55
  56 It is up to the founder and designated ops to manage a channel, not a
  57 services admin.
  58
  59 If you have problem users hacking founder passwords, surely it is better to
  60 deal with such users or (permanently) remove them from your network than
  61 start altering channel access lists.
  62
  63 &gt;<i> I can think of many legitimate situations where a service
  64 </I>&gt;<i> admin should have access control privileges globally. And on many other
  65 </I>&gt;<i> services distributions this is the case.
  66 </I>
  67 Well your single example so far can be handled far better using the current
  68 provisions of IRCServices so the ability to manipulate the access list is
  69 not required for that one.
  70
  71 IRCServices is open source so you could add your own support. It would be
  72 quite trivial to implement as a custom patch for your network.
  73
  74 If as you say &quot;many&quot; other packages offer it, maybe one of those would be
  75 better for you. A number of packages are branches of IRCServices so you are
  76 likely to find such packages very similar in operation.
  77
  78 --
  79 Mark.
  80
  81
  82
  83 </PRE>
  84
  85 <!--endarticle-->
  86     <HR>
  87     <P><UL>
  88         <!--threads-->
  89         <LI>Previous message: <A HREF="000498.html">[IRCServices Coding] Services Admin : Global Access to Channel Settings
  90 </A></li>
  91         <LI>Next message: <A HREF="000503.html">[IRCServices Coding] list
  92 </A></li>
  93          <LI> <B>Messages sorted by:</B>
  94               <a href="date.html#499">[ date ]</a>
  95               <a href="thread.html#499">[ thread ]</a>
  96               <a href="subject.html#499">[ subject ]</a>
  97               <a href="author.html#499">[ author ]</a>
  98          </LI>
  99        </UL>
 100
 101 </body></html>