View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005176 | unreal | ircd | public | 2018-12-28 14:38 | 2019-11-27 12:37 |
| Reporter | syzop | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.2.1 | ||||
| Target Version | 4.2.2-rc1 | Fixed in Version | 5.0.0-rc2 | ||
| Summary | 0005176: umode +q should only be for xx-with-override | ||||
| Description | 14:34 < PeGaSuS> Syzop[AWAY]: yes, I was talking about tying umode +q (unkickable) only to *-with-override operclasses 14:35 < PeGaSuS> I mean, we expect that *-with-override classes to be something like the highest class within the rank. otherwise any oper can use that umode. So.. make it a separate priv | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I'll look into fixing this for U5. |
|
|
commit 1e3d726df7d692f29599a55ed4ac8c2df0c7605a (HEAD -> unreal50, origin/unreal50) Author: Bram Matthys <[email protected]> Date: Wed Nov 27 12:35:58 2019 +0100 Setting user mode +q now requires the self:unkickablemode permission. This is included in the *-with-override operclasses. Sorry, forgot to credit you... |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-12-28 14:38 | syzop | New Issue | |
| 2018-12-28 14:38 | syzop | Status | new => confirmed |
| 2018-12-28 14:38 | syzop | Target Version | => 4.2.2-rc1 |
| 2019-11-20 17:24 | syzop | Relationship added | child of 0005279 |
| 2019-11-20 17:24 | syzop | Note Added: 0021111 | |
| 2019-11-27 12:37 | syzop | Assigned To | => syzop |
| 2019-11-27 12:37 | syzop | Status | confirmed => resolved |
| 2019-11-27 12:37 | syzop | Resolution | open => fixed |
| 2019-11-27 12:37 | syzop | Fixed in Version | => 5.0.0-rc2 |
| 2019-11-27 12:37 | syzop | Note Added: 0021125 |
