View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001656||Anope Stable (2.0.x series)||General||public||2015-06-24 20:57||2015-09-14 19:43|
|Summary||0001656: Expired or dropped NickServ accounts keep their opertype when registered back|
|Description||When all the aliases of a services oper are dropped or expire, the former oper is no longer listed in "/os oper list". But when the nick is registered again (even hours later), OperServ remembers it and ties their former opertype to the new nick, potentially granting them access to OperServ.|
It is the expected behavior for an oper nick configured in the config file. However, it is unexpected when the oper was not set in the file.
The opertype association with the nick should be forgotten when the nick expires or is dropped.
Expiring nickname OperNick (group: OperNick) (e-mail: OperNick@example.net)
Deleting nickname group OperNick
Tied oper OperNick to type Services Operator
COMMAND: OperNickemail@example.com used REGISTER to register OperNick (email: OperNick@example.net)
* "secureadmins" does not prevent expiration and does not help;
* "restrictopernicks" certainly helps, but the wildcard matching may be unwanted;
* "opersonly" definitely helps;
* restarting the services makes operserv to forget the nick.
|Tags||No tags attached.|