View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003696 | unreal | ircd | public | 2008-05-23 21:22 | 2008-05-23 21:32 |
| Reporter | RandomNumber | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2.7 | ||||
| Summary | 0003696: Oper override trigger. | ||||
| Description | I was curious why this sets off an override. Or why normal users can't do this. If I am +ao in a channel and I deop myself /mode #channel -o MrStatic. I still maintain +a. Now if I go to reop myself I set an override off. Now +a reads "a <nickname> = Gives Channel Admin to the user" so a>o. | ||||
| 3rd party modules | |||||
|
|
This is basically the means of how its supposed to be, +a is not a op status in itself necessarily (which is why modes such as SOP for services set +ao, not just +a). +o contains all the rights as a user to be a 'channel operator', the +a simply gives them a higher acceptance in that +o users cannot kick them as they are admins/protected. This is the same basics with +q for the most part, its 'founder' status, but with services supporting founder/+q with UnrealIRCd, you'll see they +qo a user, not just +q. This is also why it provides an override notice, as those are not op statuses themselves 'over' that of +o in short, so the IRCd views you as 'overriding' to op yourself with abilities in that channel. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-05-23 21:22 | RandomNumber | New Issue | |
| 2008-05-23 21:32 | nate | QA | => No need for QA |
| 2008-05-23 21:32 | nate | U4: Need for upstream patch | => No need for upstream InspIRCd patch |
| 2008-05-23 21:32 | nate | Status | new => closed |
| 2008-05-23 21:32 | nate | Note Added: 0015296 | |
| 2008-05-23 21:32 | nate | Resolution | open => no change required |
| 2008-05-23 21:32 | nate | Note Edited: 0015296 |
