View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003209 | unreal | ircd | public | 2007-01-23 04:38 | 2007-04-19 03:15 |
Reporter | afk | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | always |
Status | resolved | Resolution | duplicate | ||
Platform | All | OS | All | OS Version | All |
Product Version | 3.2.6 | ||||
Summary | 0003209: Big spamfilter issue. | ||||
Description | hello i have been trying to report what i find as a serirus issue. spamfiltering things like *.0* *.1* ect.. action Kill cause theres tkls for all bans but nothing i've seen for kill. this is an issue because ppl will steal olines or get mad and use there olines to set such bans. mass kill opers. and then everyone is unable to reconnect only ways i've seen to fix this are A restarting all ircds at once as restarting 1 or 2 ect when they link it will readd itself and B restarting 1. getting on it. opering then waiting for it to connect since it won't kill an oper then removing it. still either way its a pain and i feel it should be fixed such as how u can not Gline *@* ect Thanks :) hope this gets fixed and replyed too Thanks afk/Tim | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
|
Don't know if it already exists on the bugtracker, but the idea was to have a configurable thingy that would configure a threshold, if more than ..% of users would be killed/*lined, then the spamfilter would be rejected. This would be for unintentional (accidental!) bad spamfilters though. In case of intentionally bringing down the net and/or *lining everyone on it, there are too many ways of succeeding, it's not possible to help against that (like, you could just add 30 spamfilters for each letter/digit, just like you could gline all most common tld's). |
|
yea its a hard one. But is there a posibility for a module or coded TKL agunst kills ? so no one includeing spamfilter can kill cirten hosts? kinda like the tkls for gline kline shun/ect i would think that would fix the issue as well as provide more protection for network owners i like ur idea it will help with accidents as u have stated but won't help for this issue i think a tkl for kill would be useful to solve this but open to any other ideas lol :) |
|
Sounds to me more like you have some problems with your opers. You could just take the can_gkline flag out of privileges (and use services akill, etc). And no, there's no possible way to have a "kill protection" that even blocks spamfilters (there are modules for kill protection but they can't stop spamfilter since it just does exit_client), but I should point out that anyone who's actually opered won't get nuked by a spamfilter, so they could just go and remove it. [edit: on a note related to the removing the flag above, I do think it was once suggested to split off the spamfilter privilege. I'll have to find that again] [edit2: found it: 0002497] |
Date Modified | Username | Field | Change |
---|---|---|---|
2007-01-23 04:38 | afk | New Issue | |
2007-01-23 06:53 | syzop | Note Added: 0013094 | |
2007-01-23 08:34 | afk | Note Added: 0013095 | |
2007-01-23 09:22 | aquanight | Note Added: 0013096 | |
2007-01-23 09:23 | aquanight | Note Edited: 0013096 | |
2007-01-23 22:20 | aquanight | Note Edited: 0013096 | |
2007-04-19 03:15 |
|
Relationship added | duplicate of 0002497 |
2007-04-19 03:15 |
|
Duplicate ID | 0 => 2497 |
2007-04-19 03:15 |
|
Status | new => resolved |
2007-04-19 03:15 |
|
Resolution | open => duplicate |
2007-04-19 03:15 |
|
Assigned To | => stskeeps |
2007-04-19 03:15 |
|
View Status | private => public |