UnrealIRCd Forums

Hey,

Just a quick question re: NOOP - Previously on UltimateIRCd (not Unreal) a rehash (via console, eg ./ircd --HUP) would undo the NOOP command set in place via OperServ (anope services) which had been set

This doesnt happen with UnrealIRCd, even after a rehash (./unreal rehash) the NOOP command is still in place.

If your a single server, theres no way (other than a ircd restart?) to remove the NOOP command...

Is this a bug? Shouldnt a rehash clear the NOOP command?

Running UnrealIRCd 3.2 Linux
Anope IRC Services 1.7.4

Thanks,
Plasma

I'm not sure. The docs (of Anope 1.7.3) say:

-OperServ- Syntax: NOOP {SET|REVOKE} server
-OperServ- /msg OperServ HELP NOOP for more information.

As you can see, you should be able to unset the NOOP mode by issuing a /os noop revoke <servermask>. But this doesn't seem to be enough:

/os noop set server1*
*** Notice -- This server has been placed in NOOP mode
-OperServ- All O:lines of server1* have been removed.
/rehash
481 Permission Denied- You do not have the correct IRC operator privileges
/os noop revoke server1*
*** Notice -- This server is no longer in NOOP mode
-OperServ- All O:lines of server1* have been reset.
/rehash
481 Permission Denied- You do not have the correct IRC operator privileges

/mode AngryWolf -o didn't work either (couldn't reoper), I (and all other opers) had to reconnect to the server, and everything worked as usual.

I've just realized that when you enable the NOOP mode, all of your opers will lose their oper flags (my /getinfo stuff shows that clearly), and they won't come back even after disabling NOOP. Although your user modes are right, your oper flags are lost in your current session. However there are some tricks to solve this, for example like this:
(Note: to use /os oline, you have to be a Super-Admin by first enabling SuperAdmin in services.conf and doing /os set superadmin on.)

(Note2: "o" as an oper flag means local operator, while as a user mode means globop.)

I dont get what behavior your NOOP command does, but it means 'No Op' ie remove all o-lines from the server (temporary) - to prevent opers from simply rehashing the server to undo this function, all opers are killed when the command is issued.

you cant access OS when you issue NOOP (since your not opered up anymore), so you cant revoke it.

You can revoke it if your on another server... but what if you are on a 1-server based network?

Looks like a restart is needed to reinstate the olines, but a REHASH should do it.

Cant seem to get it to reinstante the olines from console via rehash, and this should work...

Help?

Oh, sorry, I was wrong when I said server masks are supported. No, they have to be full server names. So I think I found a bug in Anope, because with using server masks I weren't killed...

Actually the O:lines aren't removed (NOOP is only simulating that), hence there's no need to rehash, see:

/os noop set server2.test.com
-OperServ- All O:lines of server2.test.com have been removed.
/stats o server2*
243 O * * AngryWolf rDRhgwlcLkKbBnGAaNzWHtZv : opers(from server2.test.com)
219 o : End of /STATS report(from server2.test.com)

However I don't know how to unset the NOOP mode.

If you're on a single server network, there is no reason to ever use noop in the first place. Having it cleared on rehash would be a horrible idea. Then any admin can unset it if they have access to the shell. The purpose of noop is for test links. When you don't yet trust the admin. If the admin has the ability to remove the noop, then there would be no reason to even have noop.

codemastr wrote:The purpose of noop is for test links. When you don't yet trust the admin.

Way I would run a network is simple: don't trust the admin? don't link { } him. Same as what you would do for opers. I would probably only use NOOP if a server is going wierd (such as what happens when TS desynch occurs). If an admin is abusing his link, why NOOP? I'd just SQUIT him and drop the link {}. (Drop link {} first, then SQUIT and REHASH in one mIRC command: //rehash | //.timer 1 3 squit target.server.net). If it gets really bad, [G]ZLINEs apply to both clients and servers .

Way I would run a network is simple: don't trust the admin? don't link { } him.

And how do you do that? "Sorry, we only accept links from people we've known for at least 2 years" expect to never have more than 2-3 servers that way. Yes, opers should only be people you trust. But it's simply not practical to do that with admins. Then only people you are friends with will be able to link. And that means you'll never bring in new users. In which case, there is probably no need to link servers anyway since 2 servers can adequately handle the load of the network.

The point is, that admins should be chosen even more carefully than your opers, because when an admin has control of a server on your network, he can simply wait till the NOOP is dropped, then give himself the privs to GZLine the whole network! I don't know if this has ever happened, but it's certainly possible if you don't watch what servers you link with.

I'm not saying that you should require 100% trust (if that were possible) (i.e. same way you would do for opers), but I am saying that it's better to be able to simply link without needing to NOOP, or at least only a very short-term NOOP (like 1 day or something). If someone wants to link, you shouldn't just blindly link them and then NOOP for a month, and then after that month is up have that server start causing all kinds of problems. You investigate the server and make sure it's suitable for your network. See if the admin has a history of power abuse, because naturally, an abusive admin would be more likely to drive away more users when linked, than when not.

Yes, you should try to get to know the admin, even if it's not for 2 years, because if you know the admin, it helps both to be able to cooperate when it actually comes time to link, or when a crisis arises.

Basically, to sum it up: would you link with an admin you've never heard of?

Im not planning to link (nor do I need to right now) to other networks, I was just curious of the functionality of the NOOP command with a new IRCd, and its been answered on how to remove the NOOP command, thanks guys