View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002018 | unreal | ircd | public | 2004-08-11 21:31 | 2004-08-11 21:48 |
| Reporter | Zell | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 3.2.1 | ||||
| Summary | 0002018: Users can use /setname to evade extended ban +r set on them | ||||
| Description | Upon setting a ban on someone using a realname ban (/mode #room +b ~r:mask), they can simply use /setname and change their realname. This is because unlike /sethost, /setident, users are not checked for operator flags when typing /setname | ||||
| 3rd party modules | |||||
|
|
~r is meant to ban trojans and bots that have static realnames. It is not meant to be a way to keep users out. |
|
|
Though, the name/ident/host commands are intended to be an Opers-only command. Is the /setname left as a user command intentionally? And, couldnt someone code a flood bot to detect a realname ban being set, and have it do /setname ? edited on: 2004-08-11 21:37 |
|
|
Yes, /setname is supposed to be available to users. And the flood is irrelevant, if you want to keep a user out, use a +b, not a +b ~r. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-08-11 21:31 | Zell | New Issue | |
| 2004-08-11 21:32 |
|
Status | new => closed |
| 2004-08-11 21:32 |
|
Note Added: 0007341 | |
| 2004-08-11 21:33 | Zell | Status | closed => feedback |
| 2004-08-11 21:33 | Zell | Resolution | open => reopened |
| 2004-08-11 21:33 | Zell | Note Added: 0007342 | |
| 2004-08-11 21:37 | Zell | Note Edited: 0007342 | |
| 2004-08-11 21:48 |
|
Status | feedback => closed |
| 2004-08-11 21:48 |
|
Note Added: 0007343 |
