View Issue Details

IDProjectCategoryView StatusLast Update
0006410unrealircdpublic2024-05-19 18:50
Reporterrafaelgrether Assigned Tosyzop  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version6.1.3 
Fixed in Version6.1.6-rc1 
Summary0006410: Exempt Bans with wildcard +e ~a: is not working properly
DescriptionHi guys,

The wildcard ~a:* is not working properly, I guess.

I did a test, I created ban in a channel for user from country region to forward him to specific channel, and add an exception for only authenticated users with services.
But the wildcard +e ~a:* (or +e ~a:someaccount) is not working, the user authenticated is still banned from channel.

Above, steps to reproduce.
Steps To ReproduceI created ban for certain regions and forward:

/mode #room +b ~forward:#brasil:~country:BR
/mode #room +b ~forward:#usa:~country:US

The #room ban and forward is working perfectly.

So, I created a exempt ban for authenticated users only:

/mode #room +e ~account:*

But authenticated users are still banned in #room and cannot enter.
TagsNo tags attached.
3rd party modules

Activities

syzop

2024-05-10 17:02

administrator   ~0023186

Thanks for the report. On further testing it seems, all +e exempts don't work against a +b ~forward, including +e *!*@*

syzop

2024-05-19 18:50

administrator   ~0023188

This should now be fixed. Thanks for the report!

https://github.com/unrealircd/unrealircd/commit/b07f02fb11afceadfa72141c3bf8bcca701c6256

commit b07f02fb11afceadfa72141c3bf8bcca701c6256 (HEAD -> unreal60_dev, origin/unreal60_dev, origin/HEAD)
Author: Bram Matthys <[email protected]>
Date: Sun May 19 18:49:33 2024 +0200

    Fix +b ~forward not taking into account +e (ban exemptions).
    Reported by rafaelgrether in https://bugs.unrealircd.org/view.php?id=6410

Issue History

Date Modified Username Field Change
2024-05-09 23:22 rafaelgrether New Issue
2024-05-10 17:02 syzop Note Added: 0023186
2024-05-10 17:03 syzop Assigned To => syzop
2024-05-10 17:03 syzop Status new => confirmed
2024-05-19 18:50 syzop Status confirmed => resolved
2024-05-19 18:50 syzop Resolution open => fixed
2024-05-19 18:50 syzop Fixed in Version => 6.1.6-rc1
2024-05-19 18:50 syzop Note Added: 0023188