View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005805 | unreal | ircd | public | 2021-01-13 17:31 | 2023-03-19 11:12 |
| Reporter | nsturtz | Assigned To | syzop | ||
| Priority | normal | Severity | tweak | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 5.0.8 | ||||
| Summary | 0005805: Allow channels to be exempt from `username parted. Reason: Excess Flood` | ||||
| Description | I have a ascii channel on my network, and people keep getting killed my unrealircd for "Excess Flood" I think a good idea would be to add a way to "exempt" a channel from the flood kill. | ||||
| Tags | flood, security | ||||
| 3rd party modules | |||||
|
|
Actually my personally opinion about this suggestion is, a contrib 3rd party module that will allow the server administrator to specify in configuration his preferred channels to be excepted from nofakelag, so every user that is on that channel would have that ability for that channel. The most common 3rd module example is https://github.com/unrealircd/unrealircd-contrib/blob/master/files/nopmchannel.c Example: nofakelagchannel { name "#one"; name "#two"; } |
|
|
We could use this to exempt users as well. One possible use:
nofakelag {
exempt "#one,#two";
exempt "nick1,nick2"; //User must have umode +r (registered)
}
|
|
|
We have https://www.unrealircd.org/docs/FAQ#high-command-rate now (it did not exist yet when this bug was submitted) It allows fine tuning lag penalty per security group via lag-penalty / lag-penalty-bytes, but.. no.. not per channel. I think this is a bit too much of a niche to implement it that way and it would have various problems that I don't see as easily solvable. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-01-13 17:31 | nsturtz | New Issue | |
| 2021-01-13 17:31 | nsturtz | Tag Attached: flood | |
| 2021-01-13 17:31 | nsturtz | Tag Attached: security | |
| 2021-01-13 19:32 | westor | Note Added: 0021878 | |
| 2021-01-15 13:44 | PeGaSuS | Note Added: 0021879 | |
| 2023-03-19 11:12 | syzop | Assigned To | => syzop |
| 2023-03-19 11:12 | syzop | Status | new => closed |
| 2023-03-19 11:12 | syzop | Resolution | open => no change required |
| 2023-03-19 11:12 | syzop | Note Added: 0022786 |
