You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently client_can_send_to_channel is called first - and reveals the channel member, even if the message is later blocked by channel mode +T (MODE_NOMULTITARGET).
For MODE_NOPRIVMSGS (+n), it doesn't matter - if it is denied, the user is not on the channel. MODE_NOCOLOR and MODE_NOCTCP should be checked first.
And I agree - it took me a while to find the place where delay-join got removed, because I did not suspect client_can_send_to_channel to mutate state.
(If I could/have to rename it, I would name it client_prepare_send_to_channel.)
Currently
client_can_send_to_channel
is called first - and reveals the channel member, even if the message is later blocked by channel mode +T (MODE_NOMULTITARGET
).client_can_send_to_channel
is called here:https://github.com/quakenet/snircd/blob/master/ircd/ircd_relay.c#L102
+T is checked here:
https://github.com/quakenet/snircd/blob/master/ircd/ircd_relay.c#L110
Suggested fix:
Check for +T first.
The text was updated successfully, but these errors were encountered: