m_opersonlyjoin denies users for existing channels

[skywalker]

i use the linux version, now i'v found a bug in it.
When a non-oper try's to join a channel with users in it with a + in it, like #date+ it still gets the message "only opers my join/create new channels"
can this be solved please, or can someone tell me how to solve this?

[Stealth]

Both the Linux version and the Windows version are exactly the same.

Since I don't believe this is even possible with how the module handles JOIN events, I decided to give this a test myself on Unreal 3.2.9. I happen to be running the Windows version because I'm too lazy to try this on my server.

From one user, trying to join an empty channel:

Code: Select all

-> server.example.com JOIN #stuff+
<- :server.example.com 477 user #stuff+ :Sorry, only Opers may create channels.

From a second user, trying to join an existing channel:

Code: Select all

<- :user2!Stealthie@localhost JOIN :#stuff+
-> server.example.com MODE #stuff+
<- :server.example.com 353 user2 = #stuff+ :user2!Stealthie@localhost user!Stealthie@localhost 
<- :server.example.com 366 user2 #stuff+ :End of /NAMES list.
<- :server.example.com 324 user2 #stuff+ + 
<- :server.example.com 329 user2 #stuff+ 1332615698

I cannot reproduce what you describe. The reason this works, and will continue to always work, is because the module only hooks the JOIN event from the server. When a user joins a channel, the module checks to see if the channel exists or not. If the channel does not exist, the user is not allowed to join.

[skywalker]

the channel exists there are
a couple of bots in it all the time... its just because there is a + in the channel name, in the other channels there is no problem
but when i try to join #date18+ it gives only opers may create channels although there are 5 users in it

[skywalker]

ok, found the problem, the problem is in the webchat app not on the server it self, i will contact the webchat creator

[warg]

I also cannot reproduce. The following is debug output (... indicates removed lines for clarity):

Code: Select all

BASE CLIENT
[15:25] * Parsing: JOIN #date+ (from warg)
...
[15:25] * Sending [:irc.example.net 477 warg #date+ :Sorry, only Opers may create channels.] to warg
[15:25] * #date+ :Sorry, only Opers may create channels.
...
[15:25] * Parsing: oper test test (from warg)
...
[15:25] * Sending [:warg MODE warg :+owghaAsN] to warg
[15:25] * Sending [:irc.example.net 008 warg :Server notice mask (+kcfvGqso)] to warg
[15:25] * Sending [:irc.example.net 381 warg :You are now an IRC Operator] to warg
...
[15:26] * Parsing: JOIN #date+ (from warg)
...
[15:26] * Sending [:[email protected] JOIN :#date+] to warg
[15:26] * Sending [:irc.example.net 353 warg = #date+ :@warg ] to warg
[15:26] * Sending [:irc.example.net 366 warg #date+ :End of /NAMES list.] to warg

NEW CLIENT
[15:26] * Parsing: NICK warg__ (from *)
...
[15:27] * Parsing: JOIN #date+ (from warg__)
...
[15:27] * Sending [:[email protected] JOIN :#date+] to warg
[15:27] * Sending [:irc.example.net 353 warg__ = #date+ :warg__ @warg ] to warg__
[15:27] * Sending [:irc.example.net 366 warg__ #date+ :End of /NAMES list.] to warg__
...
[15:27] * Parsing: PART #date+ (from warg__)
...
[15:27] * Sending [:[email protected] PART #date+] to warg__
[15:27] * Sending [:[email protected] PART #date+] to warg
...