Need an IRCOp? Look no further!

magpie · Idler Joined: 18 Jan 2004 Posts: 454 Location: Essex, UK

At the risk of reversing through this discussion, I think there is some merit in having an automated service temporarily assume the nickname used by an impersonator. You needn't necessarily record passwords, rather inform the user (via the correct service) that they're talking to the wrong user.

SATAN-HHH · Eleet Joined: 29 Nov 2003 Posts: 838 Location: Texas

I don't think anyone should impersonate servcies either, even if they are a staff member of the network. This is still a major security risk and potential for major disrutpions and abuse on the network. I believe users should just be imformed that services are down at that time, so they now and that way if someone does attempt to impersonate services users would know it. Besides, the problem of impersonation of services can be easily fixed by restricting all of the services nicknames through your ircd. If someone attempts to impersonate services, I personally would inform user they are impersonating a network service, which is against the network AUP, and ask them to cease the action and change their nickname. If they continued, I'd use /kill comand with a message again stating they're impersonating network services which is against AUP and to cease the action. Final action would be a short autoban from the network. I'd also forbid or freeze that nickname.

Just my thoughts on it all.