View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001740||Anope Stable (2.0.x series)||General||public||2020-09-01 17:19||2020-09-01 17:19|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0001740: webcpanel register should check if the nickname is connected to start a KILL progress|
If you try to register a nickname from webcpanel that is already connected on the network and by default new registrations having KILL protection ON or QUICK then services doesn't start a progress to change the nickname of the connected user because it has been registered.
Connect on the network a unregistered nickname (lets say test_900)
Register on webcpanel that nickname (test_900)
Then services doesn't start a KILL progress to force a nickname change of test_900 because it has been registered from webcpanel.
I have a recommendation about this, maybe you like that idea to proceed on addition.
1. When a nickname registers from the webcpanel and that nickname is already connected on the network, check his IP if match with the IP from the webcpanel registration then automatically identify it.
2. SVSKILL that nickname if someone register that nickname from the webcpanel, so in case if someone is using that nickname on the network but he doesn't register it and someone else wants to register that nickname and he is able via webcpanel then services why not sending a SVSKILL if that nickname has been registered, so the new guy would be able to use that nickname (i know this is able via GHOST or RECOVER either).
|Tags||No tags attached.|