[IRCServices] Problem with /cs set secure and /cs set restricted

Craig Edwards brain at brainbox.winbot.co.uk
Fri Jan 3 00:45:00 PST 2003


Sorry for continual posting but after more testing it seems to be picky about which nicks it allows or doesnt allow, not based on anything i can figure out. One unregged nick successfully joined, while chanserv booted another... this seems to happen randomly... very weird.

I will stop posting now as continual posts on this subject like this are kind of pointless and i dont want to annoy anyone...

>On hindsight it appears this only happens when a non-regged nick joins... i had some regged nicks join to test it and they get kicked as expected.
>
>>Ok. after trying to drum it into my users that access lists should be used instead of modelocked keys, they complained to me there is a bug which stops them using this, this appears to be the case after a quick poke around (ircservices 5.0.6):
>>
>>If a user sets a channel to restricted, as shown here,
>>
>>[22:03] -ChanServ- Information for channel #testing:
>>[22:03] -ChanServ-         Founder: Cadavre
>>[22:03] -ChanServ-     Description: testes
>>[22:03] -ChanServ-      Registered: Jan 02 22:04:32 2003 GMT
>>[22:03] -ChanServ-       Last used: Jan 02 22:04:32 2003 GMT
>>[22:03] -ChanServ-         Options: Topic Retention, Restricted Access, Secure
>>
>>then if a user joins the channel and it is *empty*, they are not kicked, as would be expected... here is an example (i tried it with a non-registered nick, as this was the original complaint, but it appears it will let a registered user stay too):
>>
>>[22:03] --> You are now talking on #testing
>>[22:03] --- services.chatspike.net has changed the topic to: dum di dum (Cadavre)
>>[22:03] --- ChanServ sets modes [#testing +sntir-o Not-Registered-Test]
>>
>>... and no kick :/ i wasn't even identified, let alone on the access list. This means that if users who ARE on the access list join afterwards, the intruder can "pretend" to be on the access list simply by idling.
>>
>>is it just me or did chanserv used to join the channel, eject the user, stay to hold the ban for a few seconds to stop auto rejoin, then part again? I know that this is "wrong" as services arent supposed to join channels, but this was the default a few versions ago i believe and it worked fine... If this also does not work, how can i keep users out of these empty channels without resorting to a "well you have to use a bot or have idle users in it" response every time? Some of these channels are too small to have users on 24/7 all the time to hold the channel open (small alliance channels for online games)
>>
>>Also, at this moment in time i have no access to the services.* shell to check what options are set in the configuration. Is it possible an option is set that stops users being kicked out? I cant find such an option in my glance through the manual.
>>
>>(thanks to Cadavre for pointing out this problem)
>>
>>>>
>>>>RTFM (/msg ChanServ HELP SET MLOCK).
>>>>
>>>
>>>Thanks - when was this help text added? i dont think users read the help text for MLOCK, if a user knows (or thinks they know) how a command works, they dont bother to read help text on the command, they just use it :)
>>>
>>>
>>>------------------------------------------------------------------
>>>To unsubscribe or change your subscription options, visit:
>>>http://www.ircservices.za.net/mailman/listinfo/ircservices
>>
>>
>>------------------------------------------------------------------
>>To unsubscribe or change your subscription options, visit:
>>http://www.ircservices.za.net/mailman/listinfo/ircservices
>
>
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices