View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001624 | Anope Stable (2.0.x series) | General | public | 2014-11-29 01:05 | 2014-11-29 01:45 |
| Reporter | webczat | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Summary | 0001624: chanserv help should take privileges into account | ||||
| Description | Many commands in chanserv have help that, in it's contents, tells the user what level is by default required to access a given command. However, it does not take account that those defaults can be changed not only per channel, but also on the whole network, and in this case help output can be wrong in some cases in this respect. Also, not all access systems have to be loaded. | ||||
| Tags | No tags attached. | ||||
|
|
Example: this is help output of chanserv command "KICK" taken from terranova: 00:38 -- ChanServ (services@services.teranova.net): Syntax: kick channel nick [r eason] 00:38 -- ChanServ (services@services.teranova.net): kick channel mask [r eason] 00:38 -- ChanServ (services@services.teranova.net): 00:38 -- ChanServ (services@services.teranova.net): Kicks a specified nick from a channel. 00:38 -- ChanServ (services@services.teranova.net): 00:38 -- ChanServ (services@services.teranova.net): By default, limited to AOPs or those with level 5 access 00:38 -- ChanServ (services@services.teranova.net): and above on the channel. Channel founders can also specify masks. In the code, the fact that this command is restricted by default to AOPS or access level 5 is given statically, but network defaults can be changed using privilege blocks in the config, so this info may become invalid. In addition, someone may want to use chanserv with no xop module at all, for example, so it could possibly confuse users. |
