View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005312 | unreal | ircd | public | 2019-06-06 17:32 | 2020-01-02 18:02 |
| Reporter | Koragg | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 5.0.0-beta1 | ||||
| Summary | 0005312: restrict-commands config option to make given commands oper-only | ||||
| Description | It would be useful having a restrict-commands config option to make given commands oper only. This can already be done for umodes, chmodes and extbans. IMPORTANT note: It MUST "kick in" AFTER a client has successfully established a connection, so that those who wish to e.g. disable NICK will not break their network (this is also why the nick module cannot be unloaded). The config file option should ideally be space seperated (as commands are not single chars as modes/extbans) so e.g. restrict-commands "nick topic setname" (to illustrate how it could look). This option would be useful if you wish to provide functionality to opers just not to users, so unloading would not be the most suitable solution in all cases. There should be some commands IMPORTANT note again: Some commands should NEVER be allowed to be made oper only as "dummy safety" for example QUIT or PONG. Perhaps exclude ADMIN as well since even a shun excludes it too? Potentially CAP and its (now case insensitive :P) sub commands as well? OPER is another one as otherwise people cannot /OPER up ever. AUTHENTICATE might be a good candidate here as well (a bit randomly sorted by order in which they pop up in my head). Also PRIVMSG and NOTICE as otherwise the main purpose of IRC, to chat, is broken as well. Mabe JOIN should also never be made oper only? Or perhaps "link" it that "if there are auto join channels, you may disable it, otherwise not"? Any feedback would be greatly appreciated! Regards, Koragg | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Another command that should never be blocked is USER. It is only used during registration (when restrict-commands may not kick in) and after that, it only responds "you may not reregister" or "you are already registered" on most IRCd's so no reason to make it oper only either. |
|
|
UnrealIRCd 5 has this. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-06-06 17:32 | Koragg | New Issue | |
| 2019-06-06 17:56 | Koragg | Note Added: 0020723 | |
| 2020-01-02 18:02 | syzop | Assigned To | => syzop |
| 2020-01-02 18:02 | syzop | Status | new => resolved |
| 2020-01-02 18:02 | syzop | Resolution | open => fixed |
| 2020-01-02 18:02 | syzop | Fixed in Version | => 5.0.0-beta1 |
| 2020-01-02 18:02 | syzop | Note Added: 0021197 |
