View Issue Details

IDProjectCategoryView StatusLast Update
0001964unrealircdpublic2006-11-25 17:36
Reportervonitsanet Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionno change required 
Summary0001964: An irc server doesn't inform the other linked servers for someone who is a local operator
DescriptionWhy an irc server doesn't inform the other linked servers for someone who is a local operator?
Bandwith saving?
I don't think that there exist so many local operators on an irc network..
If this can be added it will fix problems with some services packages and stats packages and it will not "eat" so many Bandwith..

Cheers :-))
3rd party modules

Activities

Zell

2004-07-15 20:37

reporter   ~0007098

the umode +O/locop status has been discussed before, the reason is simply that other servers need not know about local operators, since they are local and cant do anything to the remote server, so why use its memory and bandwidth to hold information about an oper that it doesnt need...

aquanight

2004-07-15 21:25

reporter   ~0007107

Well I notice one thing... Services NOOP command, Anope/IRCServices claim to "kill all IRCops on the server" so as to prevent them from rehashing which would cancel the effect (though I believe what really happens is that all operflags are removed including can_rehash, and I don't think Unreal clears it's NOOP status on a rehash, IIRC). So while I don't know exactly what really happens, I would say that if they do really /KILL all opers on the server, they would need to know about +O users because they have rehash powers too! (However, a WHOIS nick nick would reveal the oper status quite well... :P )

codemastr

2004-07-16 16:10

reporter   ~0007113

I'm trying to figure out the results of doing this. I'm thinking about the IRCServices +O channel issue and thinking sending +O out would be a good idea. Syzop, can you foresee any problems with making this global?

Zell

2004-07-19 15:55

reporter   ~0007165

i have been using UMODE_GLOBAL for that on the LAN server (no big network... thus no problem if modifications cause crash)... and no problem so far (using 2 servers and 1 services and 1 stats) and there are no problem so far.

aquanight... a note about NOOP. when you set it thru services, it first sends the command SVSNOOP to the server then it uses /kill on anyone what was operator. it says in its docs "to prevent them from rehashing", but the IRCd already removes all their usermodes (like +oOaANC, etc) and resets their operflags in memory (like can_rehash), so if you tried /rehash right after you saw the NOOP notice, it would give you ERR_NOPRIVILEGES. it doesnt really knock out the O:Lines, it just cancels the /oper command... :)
of course, you could probably remote-rehash? :-D

syzop

2004-07-19 19:45

administrator   ~0007168

codemastr: bit hard to tell indeed. I think locops will be able to see slightly more stuff (and perhaps be able to do slightly more, dunnow).. because some commands might have an IsAnOper check.. and if the command is used in a 'remote way' by a locop the endpoint would normally get IsAnOper = false, but with the change = true... These are probably not huge security risks, but it's worth to do a little audit on IsAnOper (eg: src/modules to start with), well.. just only for commands that can be used remotely [this isn't too hard, should just take like 20-60 minutes ;p].
A simple example: remote /stats (IsAnOper=override oper-only-stats).. IMO remote locops shouldn't see oper-only-stats (like is now the case).

codemastr

2004-07-20 00:23

reporter   ~0007170

imho, we should rename those two things. IsGOper and IsOper seem to be more clear. I think alot of the IsAnOper stuff is because people often forget which one is which :P

vonitsanet

2004-08-18 10:41

reporter   ~0007390

is this added??

codemastr

2004-08-18 15:18

reporter   ~0007392

If it were added, then we would have said, "this has been added."

vonitsanet

2004-10-23 08:15

reporter   ~0008083

A little question :))))
codemastr do u know if this will be added to the next release?

syzop

2004-10-23 19:40

administrator   ~0008093

I'm sure he knows, I know it too.

vonitsanet

2006-11-25 17:16

reporter   ~0012732

*Bump* :D

syzop

2006-11-25 17:36

administrator   ~0012733

I don't see any reason to do this.
If you want a oper to be globally known, make it global.
The whole idea of a local oper is that it's LOCAL.

Checked bahamut... does the same as us
Checked hybrid... they don't even have local opers anymore (good, wished we did that as well... *grin* no I'll keep my hands off ;p)

Issue History

Date Modified Username Field Change
2004-07-15 13:20 vonitsanet New Issue
2004-07-15 20:37 Zell Note Added: 0007098
2004-07-15 21:25 aquanight Note Added: 0007107
2004-07-16 16:10 codemastr Note Added: 0007113
2004-07-19 15:55 Zell Note Added: 0007165
2004-07-19 19:45 syzop Note Added: 0007168
2004-07-20 00:23 codemastr Note Added: 0007170
2004-08-18 10:41 vonitsanet Note Added: 0007390
2004-08-18 15:18 codemastr Note Added: 0007392
2004-10-23 08:15 vonitsanet Note Added: 0008083
2004-10-23 19:40 syzop Note Added: 0008093
2006-11-25 17:16 vonitsanet Note Added: 0012732
2006-11-25 17:36 syzop Status new => closed
2006-11-25 17:36 syzop Note Added: 0012733
2006-11-25 17:36 syzop Resolution open => no change required