software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002852.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] /ns ghost exploit
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/ns%20ghost%20exploit&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="002851.html">
  11    <LINK REL="Next"  HREF="002853.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] /ns ghost exploit</H1>
  15     <B>Mark Hetherington</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/ns%20ghost%20exploit&In-Reply-To="
  17        TITLE="[IRCServices] /ns ghost exploit">mark at ctcp.net
  18        </A><BR>
  19     <I>Thu Mar 14 20:50:01 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002851.html">[IRCServices] /ns ghost exploit
  22 </A></li>
  23         <LI>Next message: <A HREF="002853.html">[IRCServices] /ns ghost exploit
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2852">[ date ]</a>
  27               <a href="thread.html#2852">[ thread ]</a>
  28               <a href="subject.html#2852">[ subject ]</a>
  29               <a href="author.html#2852">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> Andrew Church wrote:
  35 </I>&gt;<i>      C'est la vie; I don't see this as a problem Services needs to handle.
  36 </I>
  37 I see. It is a problem Services introduced so it seemed appropriate for
  38 Services to handle it :(
  39
  40 &gt;<i> If you have particular users doing this and it annoys other users, deal
  41 </I>&gt;<i> with the trouble causers individually.
  42 </I>
  43 Dealing with the current individuals concerned over this issue, does not
  44 make the problem go away. It merely creates a maintenance task each time
  45 someone new uses it. Prevention seems better than cure in this, as in any
  46 system.
  47
  48 It seems odd that I can turn off Services' own ability to kill users in
  49 various circumstances (NSForceNickChange), but must allow users the power
  50 to use Services to kill another user off the network, especially when
  51 Services is already &quot;handling&quot; the user depending on registration options.
  52 A single 'if (has_identified_nick())' (or similar) on the target would seem
  53 to be a suitable solution and is the one I will look into implementing.
  54
  55 --
  56 Mark.
  57
  58
  59
  60 </PRE>
  61
  62 <!--endarticle-->
  63     <HR>
  64     <P><UL>
  65         <!--threads-->
  66         <LI>Previous message: <A HREF="002851.html">[IRCServices] /ns ghost exploit
  67 </A></li>
  68         <LI>Next message: <A HREF="002853.html">[IRCServices] /ns ghost exploit
  69 </A></li>
  70          <LI> <B>Messages sorted by:</B>
  71               <a href="date.html#2852">[ date ]</a>
  72               <a href="thread.html#2852">[ thread ]</a>
  73               <a href="subject.html#2852">[ subject ]</a>
  74               <a href="author.html#2852">[ author ]</a>
  75          </LI>
  76        </UL>
  77
  78 </body></html>