1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices Coding] ChanServ Mode Bug?
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ChanServ%20Mode%20Bug%3F&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=
"001382.html">
11 <LINK REL=
"Next" HREF=
"001383.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices Coding] ChanServ Mode Bug?
</H1>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20ChanServ%20Mode%20Bug%3F&In-Reply-To="
17 TITLE=
"[IRCServices Coding] ChanServ Mode Bug?">arathorn at theonering.net
19 <I>Fri Sep
6 16:
03:
22 PDT
2002</I>
21 <LI>Previous message:
<A HREF=
"001382.html">[IRCServices Coding] ChanServ Mode Bug?
23 <LI>Next message:
<A HREF=
"001383.html">[IRCServices Coding] ChanServ Mode Bug?
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1385">[ date ]
</a>
27 <a href=
"thread.html#1385">[ thread ]
</a>
28 <a href=
"subject.html#1385">[ subject ]
</a>
29 <a href=
"author.html#1385">[ author ]
</a>
34 <PRE>----- Original Message -----
35 From:
"M
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">mark at ctcp.net
</A>>
36 To:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net
</A>>
37 Sent: Friday, September
06,
2002 11:
46 PM
38 Subject: RE: [IRCServices Coding] ChanServ Mode Bug?
41 ><i> Arathorn wrote:
42 </I>><i> > I can confirm that under Unreal
3.1.4 that when having given myself a
44 ><i> > on a channel of +q (using /mode whilst opered):
46 </I>><i> > /oper Arathorn password
49 </I>><i> Results snipped since your test is invalid from this point as you are an
50 </I>><i> oper and not subject to the same rules as
"normal
" users.
52 The whole point of my 'test' was that after initially opering up in order to
53 set #channel +q Arathorn - i promptly deopered (with /mode Arathorn -o). Or
54 does that still count as being 'opered'?
56 Anyway, on repeating the whole exercise whilst *not opered* (and never have
57 been opered that session) - i.e. registering a new channel to gain founder
58 status (and thus also +q on join), precisely the same behaviour is observed.
59 I can deop, but whilst I still am +q on the channel, I can op and deop any
60 other user. I repeat - at no point in any of that was I opered.
62 Please read the whole mail next time before feeling the need to shoot it
63 down in flames; I was after all just trying to provide Andrew with the
64 confirmation he requested. This behaviour doesn't pose any problem in my
65 configuration, at any rate.
69 _______________________
70 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">arathorn at theonering.net
</A>
79 <LI>Previous message:
<A HREF=
"001382.html">[IRCServices Coding] ChanServ Mode Bug?
81 <LI>Next message:
<A HREF=
"001383.html">[IRCServices Coding] ChanServ Mode Bug?
83 <LI> <B>Messages sorted by:
</B>
84 <a href=
"date.html#1385">[ date ]
</a>
85 <a href=
"thread.html#1385">[ thread ]
</a>
86 <a href=
"subject.html#1385">[ subject ]
</a>
87 <a href=
"author.html#1385">[ author ]
</a>