software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/003308.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Network Policies..
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Network%20Policies..&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="003315.html">
  11    <LINK REL="Next"  HREF="003310.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Network Policies..</H1>
  15     <B>Craig McLure</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Network%20Policies..&In-Reply-To="
  17        TITLE="[IRCServices] Network Policies..">Craig at chatspike.net
  18        </A><BR>
  19     <I>Mon Nov 18 10:51:21 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003315.html">[IRCServices] change nick
  22 </A></li>
  23         <LI>Next message: <A HREF="003310.html">[IRCServices] Network Policies..
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#3308">[ date ]</a>
  27               <a href="thread.html#3308">[ thread ]</a>
  28               <a href="subject.html#3308">[ subject ]</a>
  29               <a href="author.html#3308">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>We had a problem on our network with a &quot;Server Administrator&quot; with shell access to his server, slowly setting his network access higher, to Services admin, he also added the &quot;globalroute&quot; ability on his oper{} and started squitting some of our servers.. we promptly removed his server from the map.. it brought us to thinking.. Would there be a way to prevent this occuring in the future, some times server admins, sometimes friends, appear nice, and give you a server, then turn on you.. We originally started thinking of introducing &quot;Policies&quot; on our IRCd, but then Brain` came up with the idea of coding it into services.. OperServ or a new services would be able to control other opers, and make sure their privs havnt been changed without permission, obviously this has its problems, but we should be able to solve them.. The main Questions are..
  35
  36 Would you use it?
  37 Should it be intergrated into OperServ or a new Service Created?
  38 Should the Opers be handled via Config, or thru a database?
  39
  40 -----------------------------------------------------------------------
  41 Craig McLure - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">Craig at chatspike.net</A>
  42 ChatSpike - The users network: <A HREF="http://www.chatspike.net">http://www.chatspike.net</A>
  43 InspIRCd - Modular IRC server: <A HREF="http://www.inspircd.org">http://www.inspircd.org</A>
  44 -----------------------------------------------------------------------
  45
  46
  47
  48
  49 </PRE>
  50
  51 <!--endarticle-->
  52     <HR>
  53     <P><UL>
  54         <!--threads-->
  55         <LI>Previous message: <A HREF="003315.html">[IRCServices] change nick
  56 </A></li>
  57         <LI>Next message: <A HREF="003310.html">[IRCServices] Network Policies..
  58 </A></li>
  59          <LI> <B>Messages sorted by:</B>
  60               <a href="date.html#3308">[ date ]</a>
  61               <a href="thread.html#3308">[ thread ]</a>
  62               <a href="subject.html#3308">[ subject ]</a>
  63               <a href="author.html#3308">[ author ]</a>
  64          </LI>
  65        </UL>
  66
  67 </body></html>