View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006414 | unreal | ircd | public | 2024-05-22 14:21 | 2024-06-14 11:22 |
| Reporter | syzop | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Product Version | 6.1.5 | ||||
| Target Version | 6.1.6 | Fixed in Version | 6.1.7 | ||
| Summary | 0006414: locop can rehash remote server? | ||||
| Description | Looking at the code I noticed that we only have the server:rehash privilege, given to all default operclasses. This is also documented at such. Still, it makes more sense to require a new server:rehash:global for remote rehashes (REHASH remote.server, REHASH -global). And then not include that privilege in the locop operclass. | ||||
| 3rd party modules | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-05-22 14:21 | syzop | New Issue | |
| 2024-05-22 14:21 | syzop | Status | new => assigned |
| 2024-05-22 14:21 | syzop | Assigned To | => syzop |
| 2024-05-22 14:22 | syzop | Description Updated | |
| 2024-06-14 11:22 | syzop | Status | assigned => resolved |
| 2024-06-14 11:22 | syzop | Resolution | open => fixed |
| 2024-06-14 11:22 | syzop | Fixed in Version | => 6.1.7 |
| 2024-06-14 11:22 | syzop | Note Added: 0023221 |
