View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002333 | unreal | ircd | public | 2005-02-12 03:27 | 2005-02-26 18:13 |
| Reporter | seneces | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 3.2.3 | ||||
| Summary | 0002333: Halfops exempt from +f #t? | ||||
| Description | Currently, channel ops are exempt from flood protection (mode +f). What about halfops? I don't see any reason they shouldn't be exempt. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
On the other hand, why SHOULD they be exempt? :P |
|
|
Well, if someone is trusted enough to have halfops and the ability to kick/ban users and set (some) modes, you should hope they won't spam. |
|
|
Hope kills.. if they get hacked your screwed =) |
|
|
[quote]Hope kills.. if they get hacked your screwed =)[/quote] Irrelevant. If that's the case, no one should be exempt from +f, not even a user who is +q nor a netadmin because anyone can be hacked. In fact, we shouldn't even have +q or netadmins because that simply amplifies the problem if someone is hacked! In short, the threat of a user being hacked is never a good excuse in this context because all it does is suggest that *all* power should be removed which is not feasible. |
|
|
assigned. I presume the reporter means +f #t (per-user textflood), this indeed seems to affect halfops. |
|
|
Fixed in .288. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-02-12 03:27 | seneces | New Issue | |
| 2005-02-12 12:16 | aquanight | Note Added: 0009095 | |
| 2005-02-12 14:53 | seneces | Note Added: 0009105 | |
| 2005-02-23 11:56 | devil | Note Added: 0009264 | |
| 2005-02-24 23:55 |
|
Note Added: 0009291 | |
| 2005-02-26 17:56 | syzop | Summary | Halfops exempt from +f? => Halfops exempt from +f #t? |
| 2005-02-26 17:58 | syzop | Note Added: 0009320 | |
| 2005-02-26 17:58 | syzop | Status | new => assigned |
| 2005-02-26 18:13 | syzop | Status | assigned => resolved |
| 2005-02-26 18:13 | syzop | Fixed in Version | => 3.2.3 |
| 2005-02-26 18:13 | syzop | Resolution | open => fixed |
| 2005-02-26 18:13 | syzop | Assigned To | => syzop |
| 2005-02-26 18:13 | syzop | Note Added: 0009323 |
