View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003728 | unreal | ircd | public | 2008-08-28 20:15 | 2013-05-06 08:06 |
| Reporter | Celelibi | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| OS | ALL | OS Version | ALL | ||
| Product Version | 3.2.8 | ||||
| Fixed in Version | 3.4-alpha1 | ||||
| Summary | 0003728: extban ~n:*!*@* allowed for halfop | ||||
| Description | chmode +N is settable only for op's. But extban ~n:*!*@* is settable by halfop, so halfops could in some manner set mode +N. I'm not sure to be clear. | ||||
| Additional Information | Allowing extban ~n only for op's seems quite wired to me. That would neams that halfop could set only "some bans"... I suggest instead to allow +N for halfops. But after all, I'm not responsible for that choice... ;) | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I'm not sure it would be entirely possible to restrict the extban to only halfops, since halfops already have access to do normal bans. An extban is essentially a normal ban, so I don't think these can be allowed/restricted on an individual basis. |
|
|
http://hg.unrealircd.org/hg/unreal/rev/7fc7d15c8814 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-08-28 20:15 | Celelibi | New Issue | |
| 2009-07-24 01:23 | Stealth | Note Added: 0015899 | |
| 2013-05-06 08:06 |
|
Note Added: 0017507 | |
| 2013-05-06 08:06 |
|
Status | new => resolved |
| 2013-05-06 08:06 |
|
Fixed in Version | => 3.4-alpha1 |
| 2013-05-06 08:06 |
|
Resolution | open => fixed |
| 2013-05-06 08:06 |
|
Assigned To | => nenolod |
