[IRCServices] SECUREOPS and an odd mode change

Andrew Church achurch at achurch.org
Tue Nov 6 23:00:57 PST 2007


Just wondering if you've been able to procure a full debug log for the
problem below?  As I mentioned earlier, I'll need to see an uncut log
starting with the nickname and channel registration commands (or if
feasible, a complete log from Services startup to the error would be even
better).

  --Andrew Church
    achurch at achurch.org
    http://achurch.org/

>On 10/29/07, Andrew Church <achurch at achurch.org> wrote:
>> Hmm... I haven't been able to reproduce this or find any obvious cause.
>> Can you provide a debug log illustrating the problem, preferably starting
>> with newly-registered nicknames and channels?
>
>I registered a new user named testingnickname, created and registered
>a new channel called #testingchannel. testingnickname was not added to
>the access list. SECUREOPS was turned on for the channel, and
>testingnickname opped.
>
>[Oct 30 00:44:25.958408 2007] debug: Received: :res0 G #testingchannel
>+o testingnickname
>[Oct 30 00:44:25.958585 2007] debug: Sent: :ChanServ MODE
>#testingchannel -oa testingnickname testingnickname
>
>I've been glancing through the relevant code sections and can't seem
>to see anything either, but I'm wondering about the section on line 34
>in modes.c where you only have o and v listed for channel user modes.
>Isn't that array used to generate the flags in check_access_cumode?
>I'm relatively new to this codebase.
>
>-- 
>Bill Kramme
>Network and Services Administrator
>SlashNET IRC [http://slashnet.org/]