View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005114 | unreal | ircd | public | 2018-07-13 22:30 | 2018-09-03 08:52 |
Reporter | PeGaSuS | Assigned To | syzop | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | Unix | OS | Ubuntu | OS Version | 18.04 LTS |
Product Version | 4.0.18 | ||||
Summary | 0005114: Extbans shouldn't allow wildcards | ||||
Description | Using extbans in the format "+b ~r:*" as example, this allows to ban/stop all users from getting into the channel. IMHO extbans shouldn't allow wildcards, as a protection measure to prevent mistyped/misplaced bans. This is in some sort a duplicated of 0005113 but aims to be solved in the core. Hope this is enough understandable. Cheers | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
|
I disagree, why would extbans be any different from regular bans like *!*@* ? In case the user gets locked out, there's always /CS INVITE and /CS UNBAN from services. And of course if you don't run services then.. well.. that's your own decision.. plenty of ways to lock yourself out, including but not limited to +i +k +l (+z +R) or regular bans ;) On a more technical side there's much to say to keep wildcard support in extbans as it allows you more control. Read: more ways to keep troublemakers out. Long story short: I don't think we will every do this. It's fine if a 3rd party module wants to do it but I certainly won't do it in core. |
|
Probably the best to say is "disallow wildcard only extbans" |
|
Sorry, won't do this. |
Date Modified | Username | Field | Change |
---|---|---|---|
2018-07-13 22:30 | PeGaSuS | New Issue | |
2018-07-14 16:11 | syzop | Note Added: 0020191 | |
2018-07-14 16:13 | syzop | Note Edited: 0020191 | |
2018-07-14 16:13 | syzop | Note Edited: 0020191 | |
2018-07-21 22:29 | PeGaSuS | Note Added: 0020221 | |
2018-09-03 08:52 | syzop | Assigned To | => syzop |
2018-09-03 08:52 | syzop | Status | new => closed |
2018-09-03 08:52 | syzop | Resolution | open => no change required |
2018-09-03 08:52 | syzop | Note Added: 0020258 |