View Issue Details

IDProjectCategoryView StatusLast Update
0003682unrealircdpublic2013-01-09 10:44
Reportergoldenwolf Assigned Tosyzop  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionduplicate 
PlatformallOSFreeBSDOS Version7.0
Product Version3.2.8 
Summary0003682: Channel mode +u with +m causes certain issues
DescriptionWhen channel mode +u is engaged with mode +m, all operators can receive messages send to the channel through non-voiced users. I would think +mu would be deployed to make sure the non-voiced users cannot send any messages to channel. Commands such as /me appear awkwardly when sent through non-voiced users. What is really surprising is, non-voiced users can bypass the +ST mode if set on the channel, all colors being sent through them are not stripped and they can send channel notices even if +T is deployed. I think +u should be adjusted a bit in u4, at least making sure users cannot bypass channel modes such as +S and +T.
Steps To Reproduce//mode #channel +mu
Make sure you are the channel owner.
TagsNo tags attached.
3rd party modules

Relationships

related to 0003348 closedsyzop +mu suggestion 
related to 0004160 closedtmcarthur Channel mode +u/+mu 

Activities

Bricker

2008-04-17 15:47

reporter   ~0015269

afaik expected behavior, though old stuff, but expected none-the-less. Dev(s)?

goldenwolf

2008-04-17 16:11

reporter   ~0015270

Also found that it bypassed +C and +f, its ircd flooding the channel not the user, so +f doesnt work.

Stealth

2008-04-17 17:31

reporter   ~0015272

+mu behaves as it is intended as far as sending messages to only ops. If you want +mu to work like you suggest, use +b ~q:*!*@*. This will make it so non-voiced users are not allowed to speak (yes it works, I've considered it for some channels)

However, the +CSTf parts do need fixing

Shining Phoenix

2008-04-18 06:44

reporter   ~0015273

http://bugs.unrealircd.org/view.php?id=3348

Scroll down to my second note (The really big one).

syzop

2013-01-09 10:44

administrator   ~0017331

Discussion moved to 0004160

Issue History

Date Modified Username Field Change
2008-04-17 15:45 goldenwolf New Issue
2008-04-17 15:47 Bricker Status new => assigned
2008-04-17 15:47 Bricker Assigned To => Bricker
2008-04-17 15:47 Bricker Note Added: 0015269
2008-04-17 15:47 Bricker Status assigned => feedback
2008-04-17 16:11 goldenwolf Note Added: 0015270
2008-04-17 17:31 Stealth Note Added: 0015272
2008-04-18 06:44 Shining Phoenix Note Added: 0015273
2008-04-24 03:42 Bricker Assigned To Bricker =>
2008-04-26 07:02 Bricker Relationship added related to 0003348
2013-01-09 10:41 syzop Relationship added related to 0004160
2013-01-09 10:44 syzop Note Added: 0017331
2013-01-09 10:44 syzop Status feedback => closed
2013-01-09 10:44 syzop Assigned To => syzop
2013-01-09 10:44 syzop Resolution open => duplicate