1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] mlocking channel modes O and A
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20mlocking%20channel%20modes%20O%20and%20A&In-Reply-To=BAY104-F7F4F64840FB105CBF8430B8140%40phx.gbl">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"005123.html">
11 <LINK REL=
"Next" HREF=
"005124.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] mlocking channel modes O and A
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20mlocking%20channel%20modes%20O%20and%20A&In-Reply-To=BAY104-F7F4F64840FB105CBF8430B8140%40phx.gbl"
17 TITLE=
"[IRCServices] mlocking channel modes O and A">achurch at achurch.org
19 <I>Wed Feb
15 13:
35:
34 PST
2006</I>
21 <LI>Previous message:
<A HREF=
"005123.html">[IRCServices] mlocking channel modes O and A
23 <LI>Next message:
<A HREF=
"005124.html">[IRCServices] Support request: Services cannot connect to IRCD,
26 <LI> <B>Messages sorted by:
</B>
27 <a href=
"date.html#5125">[ date ]
</a>
28 <a href=
"thread.html#5125">[ thread ]
</a>
29 <a href=
"subject.html#5125">[ subject ]
</a>
30 <a href=
"author.html#5125">[ author ]
</a>
35 <PRE> It seems to me that this falls under the Don't Do That Then category;
36 if you mlock a channel +O and you're not an oper, well, that would be
37 pretty stupid. I don't see why Services should bother checking this case.
40 <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A>
41 <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
45 </I>><i>I'm new to this list and amn't sure if this has been discussed or whatnot,
46 </I>><i>but it appears to be the case that regular users (who are recognized channel
47 </I>><i>founders) can set mlocks regarding channel modes O and A (Opers-only and
48 </I>><i>Admins-only, respectively, on Unreal). I know that IRCServices are designed
49 </I>><i>to work with all sorts of IRCds, but with Unreal, only opers and admins
50 </I>><i>respectively are supposed to be able to set/unset channel modes O and A, so
51 </I>><i>allowing users to set it via ChanServ's modelock function allows them to
52 </I>><i>circumvent this... is there a way that IRCServices could query whether a
53 </I>><i>user is an oper (isanoper) before allowing them to set those mlocks?
59 </I>><i>------------------------------------------------------------------
60 </I>><i>To unsubscribe or change your subscription options, visit:
61 </I>><i><A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices">http://lists.ircservices.za.net/mailman/listinfo/ircservices
</A>
68 <LI>Previous message:
<A HREF=
"005123.html">[IRCServices] mlocking channel modes O and A
70 <LI>Next message:
<A HREF=
"005124.html">[IRCServices] Support request: Services cannot connect to IRCD,
73 <LI> <B>Messages sorted by:
</B>
74 <a href=
"date.html#5125">[ date ]
</a>
75 <a href=
"thread.html#5125">[ thread ]
</a>
76 <a href=
"subject.html#5125">[ subject ]
</a>
77 <a href=
"author.html#5125">[ author ]
</a>