View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001455 | unreal | ircd | public | 2003-12-27 20:35 | 2004-01-03 19:24 |
| Reporter | cyberCloWn | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta19 | ||||
| Summary | 0001455: Evading extended ban | ||||
| Description | I was reading the Changes file in the latest cvs and I thought about the following... ~r: gecos (realname) bans (ex: ~r:*Stupid_bot_script*). If the realname of a user matches this then (s)he is unable to join. Now if I ban ~r:stupid then the host [email protected] will not be allowed into the channel. What stops the user from evading this ban by using the /sethost command and then rejoining? | ||||
| 3rd party modules | |||||
|
|
You misunderstand the purpose of realname bans. You know, ~r:stupid means any people using "stupid" as a realname cannot join the channel. Of course, users can change their realnames with /setname, so they will no longer banned. But that's all what this type of ban does, not more. It's just a way to deny some kind of realnames in a channel. |
|
|
The fact that /sethost is an oper only command? |
|
|
I always thought that /sethost was a command anyone could use... EDIT: Okay woops, /setname. edited on: 12-28-03 20:32 |
|
|
/setname = for everyone (changes realname) /sethost = for ircops only (changes hostname) -.- |
|
|
Well here's the thing. I do +b somenick!*@* what's to stop someone from using /nick to evade that? I do +b *!someident@* what's to stop someone from disconnecting and changing their ident to evade that? The purpose of realname bans isn't to ban a particular person. It's to stop things like bots. Don't want eggdrops? Something like ~r:*/msg*hello* would stop a lot of them for example. It's not meant to be "SomeNick uses realname 'blah' I'm gonna ban that." If you want to ban a particular user, then there is no reason to use ~r in the first place. It's like saying that ~c (can not be in channel) bans can be evaded. I set +b ~c:#blah and the user parts #blah, now they can join. Well of course they can, though that's not evading. The condition is "the user can't be in #blah" and the user is not in #blah, therefore the user can join. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-12-27 20:35 | cyberCloWn | New Issue | |
| 2003-12-27 21:03 | AngryWolf | Note Added: 0004449 | |
| 2003-12-28 01:37 |
|
Note Added: 0004450 | |
| 2003-12-28 20:30 | cyberCloWn | Note Added: 0004453 | |
| 2003-12-28 20:32 | cyberCloWn | Note Edited: 0004453 | |
| 2003-12-28 23:35 | m0wl | Note Added: 0004455 | |
| 2003-12-29 02:24 |
|
Note Added: 0004456 | |
| 2004-01-03 19:24 | syzop | Status | new => closed |
