[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2003 / 001965.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices Coding] Chanserv patch for reg chans only
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Chanserv%20patch%20for%20reg%20chans%20only&In-Reply-To=20030313004158.SXAN24160.mta02-svc.ntlworld.com%40i-br0ked-it">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001964.html">
   <LINK REL="Next"  HREF="001966.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices Coding] Chanserv patch for reg chans only</H1>
    <B>Stefan Hudson</B> 
    <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Chanserv%20patch%20for%20reg%20chans%20only&In-Reply-To=20030313004158.SXAN24160.mta02-svc.ntlworld.com%40i-br0ked-it"
       TITLE="[IRCServices Coding] Chanserv patch for reg chans only">hudson at mbay.net
       </A><BR>
    <I>Wed Mar 12 19:22:51 PST 2003</I>
    <P><UL>
        <LI>Previous message: <A HREF="001964.html">[IRCServices Coding] Chanserv patch for reg chans only
</A></li>
        <LI>Next message: <A HREF="001966.html">[IRCServices Coding] Chanserv patch for reg chans only
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1965">[ date ]</a>
              <a href="thread.html#1965">[ thread ]</a>
              <a href="subject.html#1965">[ subject ]</a>
              <a href="author.html#1965">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Thu, Mar 13, 2003 at 12:41:49AM +0000, Craig McLure wrote:
&gt;<i> Good Job, i've checked thru it quickly, and dont see any immediate probs, This will be useful for people whos IRCds dont support the ability to &quot;forbid all channels except..&quot; and has been requested a couple of times. it also makes enabeling new channels easier as well, although, you may wanna add is_services_oper or maybe just is_oper support as well, meaning opers or services opers can join.
</I>
That was one of the questions I had when I was working on it.  I
decided on is_oper() because it seemed be used elsewhere for general
server-related exceptions - is_services_oper() only appears in
operserv.  I assume it also includes is_services_admin(), but that
already has an exception above my patch so it doesn't really matter.

The other question I had was if I should depend on the result from
get_channelinfo() or get_channel() to determine if a channel is
registered.  I found the code for get_channelinfo() in tools/convert-db.c,
and it seems to be a good bet for this, but I can't find the code for
get_channel() anywhere.  The text shows up in channels.o, but I can't
find the code in channels.c.  I feel a bit silly about this - I always
thought I was fairly good at C.

Also, I can think of a pathological case where the +b *!*@* might be a
problem.  It would show up if one oper joins an unregistered channel and
idles, then a normal user tries to join and services sets the +b.  With
some servers (unreal), this will prevent other opers from joining that
channel, since opers can't break bans and they can't use chanserv to
remove them, since the channel isn't registered.

This is a fairly unusual situation, but it might be more consistant if
the ban wasn't set.  However, does this open services up for a DOS from
a user repeatedly trying to join and getting kicked by chanserv?

Stefan
</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001964.html">[IRCServices Coding] Chanserv patch for reg chans only
</A></li>
	<LI>Next message: <A HREF="001966.html">[IRCServices Coding] Chanserv patch for reg chans only
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1965">[ date ]</a>
              <a href="thread.html#1965">[ thread ]</a>
              <a href="subject.html#1965">[ subject ]</a>
              <a href="author.html#1965">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices Coding] Chanserv patch for reg chans only
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Chanserv%20patch%20for%20reg%20chans%20only&In-Reply-To=20030313004158.SXAN24160.mta02-svc.ntlworld.com%40i-br0ked-it">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="001964.html">
	11	<LINK REL="Next" HREF="001966.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices Coding] Chanserv patch for reg chans only</H1>
	15	<B>Stefan Hudson</B>
	16	<A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Chanserv%20patch%20for%20reg%20chans%20only&In-Reply-To=20030313004158.SXAN24160.mta02-svc.ntlworld.com%40i-br0ked-it"
	17	TITLE="[IRCServices Coding] Chanserv patch for reg chans only">hudson at mbay.net
	18	</A><BR>
	19	<I>Wed Mar 12 19:22:51 PST 2003</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="001964.html">[IRCServices Coding] Chanserv patch for reg chans only
	22	</A></li>
	23	<LI>Next message: <A HREF="001966.html">[IRCServices Coding] Chanserv patch for reg chans only
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#1965">[ date ]</a>
	27	<a href="thread.html#1965">[ thread ]</a>
	28	<a href="subject.html#1965">[ subject ]</a>
	29	<a href="author.html#1965">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>On Thu, Mar 13, 2003 at 12:41:49AM +0000, Craig McLure wrote:
	35	><i> Good Job, i've checked thru it quickly, and dont see any immediate probs, This will be useful for people whos IRCds dont support the ability to "forbid all channels except.." and has been requested a couple of times. it also makes enabeling new channels easier as well, although, you may wanna add is_services_oper or maybe just is_oper support as well, meaning opers or services opers can join.
	36	</I>
	37	That was one of the questions I had when I was working on it. I
	38	decided on is_oper() because it seemed be used elsewhere for general
	39	server-related exceptions - is_services_oper() only appears in
	40	operserv. I assume it also includes is_services_admin(), but that
	41	already has an exception above my patch so it doesn't really matter.
	42
	43	The other question I had was if I should depend on the result from
	44	get_channelinfo() or get_channel() to determine if a channel is
	45	registered. I found the code for get_channelinfo() in tools/convert-db.c,
	46	and it seems to be a good bet for this, but I can't find the code for
	47	get_channel() anywhere. The text shows up in channels.o, but I can't
	48	find the code in channels.c. I feel a bit silly about this - I always
	49	thought I was fairly good at C.
	50
	51	Also, I can think of a pathological case where the +b !@* might be a
	52	problem. It would show up if one oper joins an unregistered channel and
	53	idles, then a normal user tries to join and services sets the +b. With
	54	some servers (unreal), this will prevent other opers from joining that
	55	channel, since opers can't break bans and they can't use chanserv to
	56	remove them, since the channel isn't registered.
	57
	58	This is a fairly unusual situation, but it might be more consistant if
	59	the ban wasn't set. However, does this open services up for a DOS from
	60	a user repeatedly trying to join and getting kicked by chanserv?
	61
	62	Stefan
	63	</PRE>
	64
65	<!--endarticle-->
66	<HR>
67	<P><UL>
68	<!--threads-->
69	<LI>Previous message: <A HREF="001964.html">[IRCServices Coding] Chanserv patch for reg chans only
70	</A></li>
71	<LI>Next message: <A HREF="001966.html">[IRCServices Coding] Chanserv patch for reg chans only
72	</A></li>
73	<LI> <B>Messages sorted by:</B>
74	<a href="date.html#1965">[ date ]</a>
75	<a href="thread.html#1965">[ thread ]</a>
76	<a href="subject.html#1965">[ subject ]</a>
77	<a href="author.html#1965">[ author ]</a>
78	</LI>
79	</UL>
80
81	</body></html>