software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002854.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="002853.html">
  11    <LINK REL="Next"  HREF="002855.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 22:37:00 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002853.html">[IRCServices] /ns ghost exploit
  22 </A></li>
  23         <LI>Next message: <A HREF="002855.html">[IRCServices] &#27704;&#36960;&#12398;&#24859;
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2854">[ date ]</a>
  27               <a href="thread.html#2854">[ thread ]</a>
  28               <a href="subject.html#2854">[ subject ]</a>
  29               <a href="author.html#2854">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> yeah, if the user has identified, then it is an obvious ghost, if
  35 </I>&gt;<i> the user
  36 </I>&gt;<i> hasn, then it is prolly a mistake.. then we come across access
  37 </I>&gt;<i> lists.. some
  38 </I>&gt;<i> ppl dont need to identify cause their host is in them.. could this be a
  39 </I>&gt;<i> prob?
  40 </I>
  41 Good point. I guess testing the NickServ level would be the ideal way since
  42 checking for a status of 2 would find if the nick was recognised by access
  43 list only with a status of 3 for identified.
  44
  45 If the access list is too vague it could lead to similar problems with
  46 popular ISPs and there is little to stop someone adding in a whole set of
  47 masks so maybe it is worth ignoring anything but fully identified nicks.
  48
  49 Recover and release would work in any case so might not be a huge problem
  50 and may encourage users to identify.
  51
  52
  53 --
  54 Mark.
  55
  56
  57
  58 </PRE>
  59
  60 <!--endarticle-->
  61     <HR>
  62     <P><UL>
  63         <!--threads-->
  64         <LI>Previous message: <A HREF="002853.html">[IRCServices] /ns ghost exploit
  65 </A></li>
  66         <LI>Next message: <A HREF="002855.html">[IRCServices] &#27704;&#36960;&#12398;&#24859;
  67 </A></li>
  68          <LI> <B>Messages sorted by:</B>
  69               <a href="date.html#2854">[ date ]</a>
  70               <a href="thread.html#2854">[ thread ]</a>
  71               <a href="subject.html#2854">[ subject ]</a>
  72               <a href="author.html#2854">[ author ]</a>
  73          </LI>
  74        </UL>
  75
  76 </body></html>