View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003877 | unreal | ircd | public | 2009-11-10 20:18 | 2015-05-30 15:32 |
| Reporter | seraph | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2.9-RC1 | ||||
| Summary | 0003877: A few feature requests for 3.2.9 or at least 3.3 | ||||
| Description | a few feature requests for .9: -remote error messages at remote rehash -extending /close command with optional servermask to allow remote /close -extending the /silence command to wildcard masks (*!*@*) -extending the /watch command to wildcard masks (*!*@*) -new feature: regex based nick!ident@ip:realname banlist (would save spamfilter entries and a lot of unneccessary g/gzlines at an usual clone attack) -more ideas are following (maybe) | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
-remote error messages at remote rehash possible, but tricky... -extending /close command with optional servermask to allow remote /close possible -extending the /silence command to wildcard masks (*!*@*) this command operates on existing users, hence the 401 not found numeric when the user is not online. Why? Because silence tracks nick changes, which is a big plus. It would require some fundumental changes to work on wildcards. Also, you would then have two systems... one that tracks existing users, and another one... i'm not sure if we'd want that. -extending the /watch command to wildcard masks (*!*@*) ehm... watch *!*@*.com ? We cannot allow that. I'm not in favor of this, I see too many problems. -new feature: regex based nick!ident@ip:realname banlist (would save spamfilter entries and a lot of unneccessary g/gzlines at an usual clone attack) I understand why it would be useful for users, BUT... this is unlikely to get in. Two reasons: 1) security: regexes are very complex (almost like a programming language on it's own) and pretty much all engines have bugs causing crashes or even a possibility of exploitation and.. -see 2-... 2) speed... regexes can be extremely slow. can bring the ircd to a halt. even with workarounds (like I did in spamfilter), it's not good... not good at all. |
|
|
Could this be split out to separate issues and then closed? "A few feature requests for 3.2.9 or at least 3.3" isn't that informative ;-). |
|
|
Your first request has been split off into 0004357. The rest I'm not in favor of, so I'm closing this bug. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-11-10 20:18 | seraph | New Issue | |
| 2009-11-14 11:34 | syzop | Note Added: 0015956 | |
| 2011-07-21 04:49 | ohnobinki | Note Added: 0016729 | |
| 2015-05-30 15:32 | syzop | Note Added: 0018379 | |
| 2015-05-30 15:32 | syzop | Status | new => closed |
| 2015-05-30 15:32 | syzop | Assigned To | => syzop |
| 2015-05-30 15:32 | syzop | Resolution | open => no change required |
