Anope Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001656Anope Stable (2.0.x series)[All Projects] Generalpublic2015-06-24 20:572015-09-14 19:43
Reporteralefburzmali 
Assigned ToAdam 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Summary0001656: Expired or dropped NickServ accounts keep their opertype when registered back
DescriptionWhen 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.
Additional InformationLogs:
Expiring nickname OperNick (group: OperNick) (e-mail: OperNick@example.net)
Deleting nickname group OperNick
...
Tied oper OperNick to type Services Operator
COMMAND: OperNick!user@example.net used REGISTER to register OperNick (email: OperNick@example.net)

Mitigations:
* "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.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0006753)
Adam (administrator)
2015-09-14 19:43

fixed in 8d13a35

- Issue History
Date Modified Username Field Change
2015-06-24 20:57 alefburzmali New Issue
2015-09-14 19:43 Adam Note Added: 0006753
2015-09-14 19:43 Adam Status new => resolved
2015-09-14 19:43 Adam Resolution open => fixed
2015-09-14 19:43 Adam Assigned To => Adam


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker