software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000206.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] A few new bugs/suggestions
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20A%20few%20new%20bugs/suggestions&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="000199.html">
  11    <LINK REL="Next"  HREF="000200.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] A few new bugs/suggestions</H1>
  15     <B>Mark Hetherington</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20A%20few%20new%20bugs/suggestions&In-Reply-To="
  17        TITLE="[IRCServices Coding] A few new bugs/suggestions">mark at mhetherington.demon.co.uk
  18        </A><BR>
  19     <I>Tue Feb  5 15:41:55 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000199.html">[IRCServices Coding] Nickname linking/coding question
  22 </A></li>
  23         <LI>Next message: <A HREF="000200.html">[IRCServices Coding] Services 5.0 alpha 19 released
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#206">[ date ]</a>
  27               <a href="thread.html#206">[ thread ]</a>
  28               <a href="subject.html#206">[ subject ]</a>
  29               <a href="author.html#206">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>1) EnableGetPass setting in Services 5.0a19 problem. The help removal when
  35 not enabled works perfectly but the directive only affects the help messages
  36 at the moment. The command itself is still accessible. Basically it is
  37 missing an
  38         if (EnableGetpass)
  39 around the code in chanserv and nickserv main.c, or an
  40         if (!EnableGetpass) possibly_do_some_message_then_return;
  41
  42 2) Minor cosmetic issue with the new oper only mention of the list command
  43 on the Chanserv help display. Since CHAN_OPER_HELP_COMMANDS_FORBID includes
  44 4 commands and then a reference to extra powers on DROP etc, it might look
  45 better if the list command check and print was before the forbid command in
  46 the help display so that the text flows correctly.
  47
  48 3) This problem actually happened on 5.0a18 but I have been unable to
  49 reproduce on that version so it might still be in 5.0a19. I am reporting for
  50 the record while I research further. From the log file:
  51
  52 PANIC! buffer = :gaspode2 PRIVMSG <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ChanServ at services.ctcp.net</A> :akick
  53 #xdigital add *~woody@*!*
  54 Services terminating: Segmentation fault
  55
  56 When trying to reproduce myself, I did notice that services reformats the
  57 mask to:
  58
  59 *~woody@*!*@*
  60
  61 Looking at the code, it is easy to see why it reformats in this manner, but
  62 I wonder if this was at all contributory to the crash.
  63
  64 This creates a couple of suggestions in addition to the crash report.
  65
  66 A) Maybe it would be possible to check for the ordering of *!*@* and reject
  67 immediately rather than creating an even more erroneous mask for entry into
  68 the akick list. This would be helpful to users creating masks.
  69
  70 B) Could the mask format be added to the help for AKICK or at least a
  71 reference to another help reference available to users that describes masks
  72 accurately. Maybe some examples similar to those for nickserv access lists.
  73
  74 I will try and get as many people as possible testing the akick comand to
  75 attempt to get a reproducable case.
  76
  77 While writing this, I have managed to get a different user reproducing it
  78 with pretty much any other user. I am not sure what the pattern is since I
  79 am still unable to produce the problem myself.
  80
  81 An IRCop/Services Admin with a Nickserv status of 0 can obviously manipulate
  82 the akick list of any channel and this will produce the problem everytime.
  83 For users to have the problem, it seems that they need to be NS status 2
  84 (recognised by access list but not by password) to reproduce the problem. I
  85 am still working on the exact scenario, but it does seem to be related to
  86 NickServ level when issuing the command.
  87
  88
  89 4) Although documented as an issue wrt to the httpd display, the channel '#'
  90 seems to have various other problems that are possibly related to IRCd and
  91 clients (for example invisible to /list regardless of oper level). This
  92 seems to make it preferable that the channel is not actually supported by
  93 services at all particularly if is has problems with any area of services
  94 functionality (e.g. httpd module).
  95
  96 I know the simple workaround is to forbid the channel but on a new
  97 installation, anything potentially erroneous ought to be guarded against.
  98 The user on our network who registered that channel did it purely because it
  99 is usually banned on networks or causes severe problems with other services
 100 packages and appears to be an exploit that various people try to abuse. It
 101 is encouraging that it has so little effect wrt IRCServices, but if there
 102 are any potential long term problems, IMO it is worth addressing sooner
 103 rather than later.
 104
 105
 106 Mark.
 107
 108
 109 </PRE>
 110
 111 <!--endarticle-->
 112     <HR>
 113     <P><UL>
 114         <!--threads-->
 115         <LI>Previous message: <A HREF="000199.html">[IRCServices Coding] Nickname linking/coding question
 116 </A></li>
 117         <LI>Next message: <A HREF="000200.html">[IRCServices Coding] Services 5.0 alpha 19 released
 118 </A></li>
 119          <LI> <B>Messages sorted by:</B>
 120               <a href="date.html#206">[ date ]</a>
 121               <a href="thread.html#206">[ thread ]</a>
 122               <a href="subject.html#206">[ subject ]</a>
 123               <a href="author.html#206">[ author ]</a>
 124          </LI>
 125        </UL>
 126
 127 </body></html>