Regarding *!*@*.* see Isomer's email. There IS enough security. Regarding what to do when your username is hacked on undernet...
First, go to http://cservice.undernet.org/live/ login (if you still can) and change your password, if you cannot login, use forgotten password (link both in side bar and right below where to login). Failing those to options, email [EMAIL PROTECTED], if still no help, then as a last resort try [EMAIL PROTECTED] [EMAIL PROTECTED] only comes into the picture when you see someone else's username is hacked and being abused. (and even then this should be verified by asking in #CService) (Please give all email addresses 5 days to reply, if no reply after 5 days resend the email) Regards [EMAIL PROTECTED] Official CService Admin On 18/5/02 4:55, "Alexander Maassen" <[EMAIL PROTECTED]> wrote: > Hello Cosmin, > > Friday, May 17, 2002, 2:50:20 PM, you wrote: > > CM> Hello. > > CM> Almost everybody knows that if you have sufficient > CM> access in a channel to set a ban through X and you set > CM> that ban on *!*@*.* X will kick all users from that > CM> channel. You need access level >= ban level to remove > CM> it. The problem is that the username's password can be > CM> stolen. So, with a stolen password and sufficient > CM> access you can kick out an entire channel. This > CM> sucks... > CM> My proposal is to add a new channel setting (level > CM> 500). For example FULLBAN (OFF or ON) which allow (or > CM> not) users to set bans on *.* . I guess is a good > CM> ideea... 10x & please excuse my english. > > CM> Best regards, > CM> JL` > > > CM> __________________________________________________ > CM> Do You Yahoo!? > CM> LAUNCH - Your Yahoo! Music Experience > CM> http://launch.yahoo.com > > Nice idea, but there is one problem. If you have looked at the > mailingarchive you would see this problem has been discussed before > and noone seems to care about it. Sounds harsch and is a personal > opinion. But likely to be a fact. > Stolen usernames are considered a lack of security on the clients side > where the user has not put enough efforts into securing his data. Thus > in case of a compromised client the client is on his own and needs to > act damn quickly in immediately mailing [EMAIL PROTECTED] . > The problem that accompanies it that this mailbox receives massive > amounts of mail, so before they read it could take a couple of days. > > My opinion is to completly remove the option to be able to use *!*@* > as kick/ban mask. (Run: you stated you would use it to clean up your banlist, > so it > would only be needed to UNBAN, no need to use it for BAN/KICK in this > matter) >
