Automatic op-up via NickServ

[reesericci]

Hello,

I am a bit of a newbie IRC operator, so forgive me if I am missing something, but I am getting hung up on operators and NickServ registrations being different. I would like to set it up where when a nick logs in over SASL, they are assigned operator privileges as that nick, rather than logging into a separate nick with a separate password for operator privileges. Is this possible?

[slingamn]

The oper names in the config are not nicknames and can be accessed from any nickname. For example, the name in the default config is admin:

ergo/default.yaml

Lines 749 to 752 in c79b65c

	opers:
	# default operator named 'admin'; log in with /OPER admin <password>
	admin:
	# which capabilities this oper has access to

but you don't have to be using the admin nick to use it, you can issue /oper admin mysecretpassword from any nickname and you'll gain operator privileges. Moreover, if you're always-on (see the userguide if you haven't already), you only need to do this once after the server is restarted. Then every time you log into your nickname with SASL, you'll have access to the privileges.

Does that help?

[reesericci]

Ah, interesting, so they're just role names, this definitely helps. However, I'm wondering if I can permanently assign a role to a NickServ "account" so that extra step is unnecessary

[slingamn]

Not directly supported. The closest thing we have is "auto-oper" via certificate fingerprint:

ergo/default.yaml

Lines 776 to 782 in c79b65c

	# if a SHA-256 certificate fingerprint is configured here, then it will be
	# required to /OPER. if you comment out the password hash above, then you can
	# /OPER without a password.
	#certfp: "abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789"
	# if 'auto' is set (and no password hash is set), operator permissions will be
	# granted automatically as soon as you connect with the right fingerprint.
	#auto: true

where you could register the same certificate fingerprint with NICKSERV CERT.

[reesericci]

Ok, let's keep this as a tracker issue then if it's something people would be interested in

[slingamn]

I'm OK with leaving this open, but I want to note my skepticism: in a traditional ircd setup, these systems (ircops and NickServ) are fully decoupled and orthogonal. SASL'ing to an oper'ed up account was an exception we introduced in Ergo that I felt was worth accepting (because it made the implementation simpler, rather than more complex). But in the absence of a really compelling reason to do so, I don't want to add any further coupling here.