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

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Feature Request: SA can modify every NS acc list
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Feature%20Request%3A%20SA%20can%20modify%20every%20NS%20acc%20list&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="004207.html">
  11    <LINK REL="Next"  HREF="004213.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Feature Request: SA can modify every NS acc list</H1>
  15     <B>Wolfgang Urban</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Feature%20Request%3A%20SA%20can%20modify%20every%20NS%20acc%20list&In-Reply-To="
  17        TITLE="[IRCServices] Feature Request: SA can modify every NS acc list">ircservices at tou.de
  18        </A><BR>
  19     <I>Mon Apr 12 07:42:21 PDT 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="004207.html">[IRCServices] Segfault again.
  22 </A></li>
  23         <LI>Next message: <A HREF="004213.html">[IRCServices] Feature Request: SA can modify every NS acc list
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#4208">[ date ]</a>
  27               <a href="thread.html#4208">[ thread ]</a>
  28               <a href="subject.html#4208">[ subject ]</a>
  29               <a href="author.html#4208">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Hi,
  35
  36 at our net we have lot of users running unattended bouncers. Some of these
  37 bouncers have no auto identify on logon and start to 'fight' with the
  38 services after a reconnect. Means: They change to a registered nick,
  39 services change their nick to a guest nick and so on - i'm sure you all know
  40 this situation.
  41
  42 I see the following options to cope with this problem (manually, as sadmin):
  43 - ban the user in one of his channels to stop nick changes
  44   You need chanop-privileges in one of the users channels. If the bouncer
  45   reconnects, you have the same problem.
  46
  47 - kill/kline the user
  48   Very hard method with low effect. BNC continues annoying by (quickly)
  49   reconnecting servers.
  50
  51 - drop the nick
  52   There should be no reason to drop other users nick.. :)
  53
  54 - disable the kill-option for the nick
  55   Working solution, but opens a security hole: Other users can use the nick.
  56
  57 - add the ident/host mask to the nick accesslist
  58   IMHO the best solution. I'm not a fan of changing other users options, but
  59   compared to the alternatives it's the easiest and friendliest method.
  60
  61 The problem is, that you can only modify your own nick access list, even as
  62 sadmin. It would be very helpful if sadmins could modify the nick
  63 access lists of any user like they can change the nick options for everyone.
  64
  65 Wolle
  66
  67
  68
  69
  70 </PRE>
  71
  72 <!--endarticle-->
  73     <HR>
  74     <P><UL>
  75         <!--threads-->
  76         <LI>Previous message: <A HREF="004207.html">[IRCServices] Segfault again.
  77 </A></li>
  78         <LI>Next message: <A HREF="004213.html">[IRCServices] Feature Request: SA can modify every NS acc list
  79 </A></li>
  80          <LI> <B>Messages sorted by:</B>
  81               <a href="date.html#4208">[ date ]</a>
  82               <a href="thread.html#4208">[ thread ]</a>
  83               <a href="subject.html#4208">[ subject ]</a>
  84               <a href="author.html#4208">[ author ]</a>
  85          </LI>
  86        </UL>
  87
  88 </body></html>