software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000473.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Services to /msg Instead of /notice
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20to%20/msg%20Instead%20of%20/notice&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="000472.html">
  11    <LINK REL="Next"  HREF="000474.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Services to /msg Instead of /notice</H1>
  15     <B>Chris Knipe</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20to%20/msg%20Instead%20of%20/notice&In-Reply-To="
  17        TITLE="[IRCServices] Services to /msg Instead of /notice">cgknipe at mweb.co.za
  18        </A><BR>
  19     <I>Thu Feb 17 09:39:02 PST 2000</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000472.html">[IRCServices] RE: Services freak out
  22 </A></li>
  23         <LI>Next message: <A HREF="000474.html">[IRCServices] ircu and Services...
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#473">[ date ]</a>
  27               <a href="thread.html#473">[ thread ]</a>
  28               <a href="subject.html#473">[ subject ]</a>
  29               <a href="author.html#473">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Andrew...
  35
  36 Realising and taking in consideration what you just mentioned below....  Is
  37 it perhaps possible to implement something in services that will actually
  38 PROTECT the Services at staying RFC comliant, and not allowing users /
  39 script kiddies / wannabe programmers to mess with the RFC standards ?
  40
  41 For example, the fact that the RFC strickly prohibits the automatic reply in
  42 notice form to any notice received from services....
  43
  44 NickServ NOTICE NICKNAME: TEXT
  45 NICKNAME NOTICE NickServ: TEXT  &lt;-- NOT allowed
  46
  47 And various other matters that are discussed in details in the RFC...
  48
  49 Perhaps implement some &quot;security&quot; or protection in those regards as to
  50 killing the user on sight with an message regarding to the fact that the
  51 user's actions is disallowed by the RFC ?  Or even just having services to
  52 ignore all notices it receives from lusers, and the like... (Which can also
  53 include the matter of pinging the services bots - it can be used in a attack
  54 against someone's IRC network when things can start slowing down and lagging
  55 quite a bit due to the services using all resources to respond to ping
  56 requests).
  57
  58 As to the first request of this luser of the threat.... It seems he only
  59 wanted help messages to go privmsg....   Seeing that, especially with
  60 HelpServ, the luser will basically be going into dialog with the services,
  61 requesting detailed help, and receiving quite a bit of text back from
  62 HelpServ.  Once again, me also want to see Services stick to RFC standards
  63 and all - for various reasons, might it not be for better interest into
  64 having helpserv, or the help commands (which returns or can return a big
  65 amount of text) use privmsgs ?
  66
  67 Just an odd idea and suggestion...
  68
  69 Regards
  70 Chris
  71
  72 ----- Original Message -----
  73 From: Andrew Kempe &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">andrewk at icon.co.za</A>&gt;
  74 To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ender.shadowfire.org</A>&gt;
  75 Sent: Wednesday, February 09, 2000 9:27 AM
  76 Subject: Re: [IRCServices] Services to /msg Instead of /notice
  77
  78
  79 &gt;<i> I _hate_ doing this, but please let's drop this thread.
  80 </I>&gt;<i>
  81 </I>&gt;<i> I (and a lot of other people) don't care who has implemented this, how it
  82 </I>&gt;<i> works etc. The fact is that it breaks the RFC and it's not going to get
  83 </I>&gt;<i> implemented here. If people want to break the RFC, then they must go on a
  84 </I>&gt;<i> private mission to do that.
  85 </I>&gt;<i>
  86 </I>&gt;<i> Andrew
  87 </I>
  88
  89
  90 ---------------------------------------------------------------
  91 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
  92 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
  93
  94 </PRE>
  95
  96 <!--endarticle-->
  97     <HR>
  98     <P><UL>
  99         <!--threads-->
 100         <LI>Previous message: <A HREF="000472.html">[IRCServices] RE: Services freak out
 101 </A></li>
 102         <LI>Next message: <A HREF="000474.html">[IRCServices] ircu and Services...
 103 </A></li>
 104          <LI> <B>Messages sorted by:</B>
 105               <a href="date.html#473">[ date ]</a>
 106               <a href="thread.html#473">[ thread ]</a>
 107               <a href="subject.html#473">[ subject ]</a>
 108               <a href="author.html#473">[ author ]</a>
 109          </LI>
 110        </UL>
 111
 112 </body></html>