Until something is done about it, here's a tip.... I've had issues with someone using this method to impersonate Saralee- on several occasions, threatening to purge our channel if we didn't give him/her our private tcl script.... Some scripts (like Peace & Protection 4.0*) actually warn you if a channel in their /whois contains control codes.. Otherwise, I would recommend joining the actual channel they're pretending to be ops in and ensure they're really an op in the actual channel. If not, ban them, and/or report them to cservice/opers. Don't just double-click the fake channel in their /whois, they'll be sure to pretend the fake channel is the real one.....
You can also /msg X verify Nick, and X will tell you what kind of access they have. Until something is done to prevent control codes in channels, this is a foolproof way to ensure that a "cservice rep/admin" is really a cservice rep/admin..... At 02:10 AM 3/12/2002 -0500, you wrote: >This came to cservice, and I know this topic has come up before. Is there >a hard code fix for this? Could and should there be? Yes this is primarily >a problem with Mirc users but it's a common "exploit" of Undernet's >services. It seems people have now found a new use for this, spamming to >get innocent channels in trouble with cservice and IRCops. >stoney`
