View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003305 | unreal | ircd | public | 2007-04-27 21:52 | 2015-08-08 08:47 |
| Reporter | craftsman | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | i386 | OS | freeBSD | OS Version | 6.2 |
| Product Version | 3.2.6 | ||||
| Fixed in Version | 3.4-beta2 | ||||
| Summary | 0003305: set::oper-only-snomasks | ||||
| Description | [19:22] * craftsman sets mode: +s - Server notice mask (+ks) - [19:22] -adrenaline.redsonora.net- *** Notice -- Received KILL message for [email protected] from craftsman Path: staff.redsonora.net!craftsman (bum) | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| 3rd party modules | |||||
|
|
what? |
|
|
What he really means is that he wants kill notices to go to irc operators or something. I think. My impression is however that users may have an interest in seeing who kills who, as a counterweight to oper abuse? |
|
|
Usermode s often gets restricted to opers only, so that "counterweighting" might not happen often. |
|
|
only that the message is for the IRC Operators just. that it does not stop users normal that they use +s |
|
|
My opinion is to keep 's' umode oper-only by default.. |
|
|
some networks like this so users can keep an eye on opers' actions, some networks don't (latter is a majority I think). As said, you can put 's' in set::restrict-usermodes to disable this behavior at the moment (as suggested in the security part of unreal32docs). We should definitely keep the feature available, but.. IMO we should default to not allowing users (non-opers) to set snomasks, but still allow it to be turned on in the conf. We'd do this by introducing a separate yes/no setting (set::snomasks-for-users, set::allow-user-snomasks, set::oper-only-snomasks, I've no idea..). |
|
|
I think calling it set::oper-only-snomasks is the best name then, comparing to the other existing oper-only setting, set::oper-only-stats, as it then corresponds with the naming scheme. :) |
|
|
If no one else plans on playing with this, I'll get to in some time this week. |
|
|
then I will play. |
|
|
Implement set::oper-only-snomasks and make it default to "*" ? |
|
|
Fixed or soon will be. All the snomask +s magic is done. The snomask +k is still umode_allow_all at this point but I made a new bug to modularize it and change default to oper |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-04-27 21:52 | craftsman | New Issue | |
| 2007-04-28 00:05 | Bricker | Note Added: 0013900 | |
| 2007-04-28 00:45 |
|
Note Added: 0013901 | |
| 2007-04-28 00:46 |
|
Status | new => feedback |
| 2007-04-28 01:23 | Shining Phoenix | Note Added: 0013902 | |
| 2007-04-28 03:48 | craftsman | Note Added: 0013903 | |
| 2007-04-29 18:46 | vonitsanet | Note Added: 0013938 | |
| 2007-04-30 00:37 | craftsman | File Added: umodes.c | |
| 2007-04-30 10:15 | syzop | Note Added: 0013950 | |
| 2007-04-30 10:17 | syzop | Status | feedback => acknowledged |
| 2007-05-05 21:58 | Robby22 | Note Added: 0014007 | |
| 2007-05-07 04:44 |
|
Summary | message kill HIDE only IRC Operators.. => set::oper-only-snomasks |
| 2007-05-19 19:33 | WolfSage | Status | acknowledged => assigned |
| 2007-05-19 19:33 | WolfSage | Assigned To | => WolfSage |
| 2007-05-19 19:33 | WolfSage | Note Added: 0014185 | |
| 2007-06-20 22:53 | craftsman | Note Added: 0014395 | |
| 2013-01-09 10:04 | syzop | Note Added: 0017310 | |
| 2013-01-09 10:04 | syzop | Assigned To | WolfSage => |
| 2013-01-09 10:04 | syzop | Severity | minor => feature |
| 2013-01-09 10:04 | syzop | Status | assigned => acknowledged |
| 2015-08-08 08:47 | syzop | Note Added: 0018580 | |
| 2015-08-08 08:47 | syzop | Status | acknowledged => resolved |
| 2015-08-08 08:47 | syzop | Fixed in Version | => 3.4-beta2 |
| 2015-08-08 08:47 | syzop | Resolution | open => fixed |
| 2015-08-08 08:47 | syzop | Assigned To | => syzop |
