View Issue Details

IDProjectCategoryView StatusLast Update
0001012unrealircdpublic2003-11-20 19:43
ReporterMichi Assigned Tosyzop  
PrioritynormalSeveritytrivialReproducibilityalways
Status closedResolutionfixed 
Product Version3.2-beta17 
Summary0001012: A few OperOverride notice bugs
DescriptionIf a oper is no channel op he can kick all people (also +oaq) thats ok..
but it the oper is a op in the channel himself than unreal only sends the normal "error" back..
I dont think that that is ok so :)
3rd party modules

Activities

syzop

2003-06-01 01:33

administrator   ~0002902

Last edited: 2003-06-01 01:34

Seems to work fine here:
OPER -o, VICTIM -o: msg sent
OPER +o, VICTIM -o: not sent
OPER +o, VICTIM +o: not sent
OPER -o, VICTIM +o: msg sent

I know some operoverride things were corrected between b16 and now, but I thought that was only topic and mode.. but.. not sure :P

edited on: 06-01-03 01:34

Michi

2003-06-01 11:04

reporter   ~0002909

Sure that you arent trying it as a NetAdmin?

* A2 sets mode: +oaq Fry Fry Fry
* A2 sets mode: -qao Michi Michi Michi
-heaven.nexusirc.org- *** OperOverride -- Michi (~Michi@localhost) KICK #michi Fry (test)
* Fry was kicked by Michi (test)

* A2 sets mode: +oaq Fry Fry Fry
* A2 sets mode: +o Michi
-heaven.nexusirc.org- *** You cannot kick Fry from #michi because Fry is channel admin

syzop

2003-06-01 16:54

administrator   ~0002910

Trying as netadmin with can_override yes, and you?
[OPER +o, VICTIM +aoq: msg sent
 OPER -o, VICTIM +aoq: msg sent]

Michi

2003-06-01 18:03

reporter   ~0002911

As a server admin.. or something less then NetAdmin what ever you want

NetAdmins have there own "way" to kick in channel.c

syzop

2003-06-18 23:17

administrator   ~0002990

Last edited: 2003-09-14 16:12

*add another operoverride bug (not tested)*

[01:13:44] <DiGiTAL-BiT> if i am ircop, and founder of a channel, how come i get OperOverride when i set +a on another user?

**edit: that's not a bug, a +a cannot +a***

edited on: 09-14-03 16:12

syzop

2003-09-14 03:33

administrator   ~0003648

*add on todo*

Rocko

2003-09-15 22:13

reporter   ~0003657

Thats right. That isn't a new bug AFAIK ;)
I noticed that earlier.

And here my other experience I made:

When I set -N (and are only ServicesAdmin), are opped, and try to kick.. don't work. When I set -o myself.. don't work. When I set +N .. don't work too. When I give myself op and try to kick, it works.
Or the other way: I set -N, have op, deop myself, try to kick, it works..
(tested on users with "channel mode" +oa, and without usermode q)
Don't forget the usermode +q, because only Services and Netadmins are able to kick such persons.

I think, that need some intensive testing, befor you close this bug report :P

syzop

2003-09-15 22:46

administrator   ~0003659

Yeah well it was some attempt to restrict kicking of channel owners (+q) and channel admins (+a) to netadmins only, but since we now got can_override I don't see any reason to have that in anymore. Reason I didn't fix it immediately is that the code is complicated. operoverride is a total mess anyway, as you might have noticed by the amount of bugs :p.

syzop

2003-10-31 19:10

administrator   ~0003906

Fixed in .1967. I might partially rewrite the oper override code in the future because there are still other "bugs".

Issue History

Date Modified Username Field Change
2003-06-01 00:53 Michi New Issue
2003-06-01 01:33 syzop Note Added: 0002902
2003-06-01 01:34 syzop Note Edited: 0002902
2003-06-01 11:04 Michi Note Added: 0002909
2003-06-01 16:54 syzop Note Added: 0002910
2003-06-01 18:03 Michi Note Added: 0002911
2003-06-18 23:17 syzop Note Added: 0002990
2003-06-18 23:18 syzop Product Version 3.2-beta16 => 3.2-beta17
2003-06-18 23:18 syzop Summary OperOverride KICK is only working if the oper isnt op in the channel => A few OperOverride notice bugs
2003-09-14 03:33 syzop Note Added: 0003648
2003-09-14 16:12 syzop Note Edited: 0002990
2003-09-15 22:13 Rocko Note Added: 0003657
2003-09-15 22:46 syzop Note Added: 0003659
2003-10-31 19:10 syzop Status new => resolved
2003-10-31 19:10 syzop Resolution open => fixed
2003-10-31 19:10 syzop Assigned To => syzop
2003-10-31 19:10 syzop Note Added: 0003906
2003-11-20 19:43 syzop Status resolved => closed