View Issue Details

IDProjectCategoryView StatusLast Update
0002918unrealircdpublic2006-05-18 05:23
Reporterw00t Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version3.2.5 
Summary0002918: SVSO discrepancy
DescriptionDespite the protocol doc recommending SVSO for the addition of IRC operator status, SVSMODE +oO will add a user to the oper fdlist, SVSO does not appear to do the same.

Perhaps it should.
3rd party modules

Activities

syzop

2006-05-17 06:31

administrator   ~0011717

Isn't SVSO for operflags and SVSMODE for usermodes? Isn't giving operflags to someone completely useless without giving the opermode? In other words, shouldn't they *always* be used both? (eg: SVSO first, then SVSMODE)
Sounds silly to then to add to operfdlist in both.. :P

Just taking a quick peek at serverprotocol.html, it seems to explain this well.

aquanight

2006-05-17 22:35

reporter   ~0011723

Actually, it's not. grep -r OPCan * in src/ and see how many of those tests don't come with an IsAnOper test. I've found that /locops, /globops, /unkline*, /unzline*, /wallops, /rehash, /restart, /die, and /notice $<server> rely only on the operflag and don't test for Is(An)Oper. Yeah, not a whole lot you can do without having the actual +o badge ;) .

* = Of course these two count for zero since they just spew "deprecated command" and otherwise do nothing.

syzop

2006-05-18 05:23

administrator   ~0011724

Yeah that's true, some don't do double checks, I had noticed that before when there was an exploit a few years ago (gotto love beta's ;p).

Anyway.. what I meant is that it's not useful, and it's illogical to add people twice to the oper fd list.

Issue History

Date Modified Username Field Change
2006-05-17 01:02 w00t New Issue
2006-05-17 06:31 syzop Note Added: 0011717
2006-05-17 22:35 aquanight Note Added: 0011723
2006-05-18 05:23 syzop Status new => closed
2006-05-18 05:23 syzop Note Added: 0011724
2006-05-18 05:23 syzop Resolution open => no change required