View Issue Details

IDProjectCategoryView StatusLast Update
0001811unrealircdpublic2004-05-17 20:37
Reporterbleepy Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionopen 
Summary0001811: Spamfilter virus-help-channel suggestion
Description1. I think it would be better if the spamfilter::virus-help-channel is "restricted" so that only opers and users who trigger a spamfilter can join it. This would help stop infected users being exploited by others.

2. Also, on more of an "appearence" note.. if the infected user is the only one there when they join, then maybe the server should deop them? I know they can't kick or do anything, but an infected user shouldn't be opped in a cleaning channel. But that's just for appearance sakes.
3rd party modules

Activities

aquanight

2004-05-12 09:43

reporter   ~0006200

Try using deny channel on it. Since the IRCd fjoins you it should override any restrictions (+bikl and deny channel), and opers can join restricted chans no matter what.

syzop

2004-05-12 11:47

administrator   ~0006202

Actually it IS a 'normal' join, no overrides :P.

I personally disagree on the dont-allow-anyone-else thing.. I would probably just name it #virus and set it +s?... But I can understand your concerns.. like some fun people could do /invite victim #virus (which we could block, but see next) or stuff like 'hey join #virus,sucks' or whatever... Then again, you might also be able to trick these kind of people into saying something that spamfilter would catch (and thus join them to #virus), but that's usually harder and more obvious.

So, perhaps an additional option :).

aquanight

2004-05-12 13:24

reporter   ~0006203

>Actually it IS a 'normal' join, no overrides :P.

So if you put invite-only/key and someone sets off a spamfilter, they're screwed ;O ? (Of course, if this happens, you can /sajoin the poor guy, but that's more work for the admins ;) .)

On the other hand, this fact plus a limit can make it easier on the opers you put in charge of running the virus channel.

As for #2 (de-op a user that creates the virus channel when setting of a spamfilter), just ChanServ it!

w00t

2004-05-12 20:05

reporter   ~0006217

Why a normal join? I agree this seems somewhat silly. Is it possible to change this?

syzop

2004-05-12 21:33

administrator   ~0006220

There's absolutely NO good reason why this should be changed, so no.. it won't happen.

w00t

2004-05-13 01:27

reporter   ~0006223

"So if you put invite-only/key and someone sets off a spamfilter, they're screwed ;O ?" I woulda thought this was a reason, but mkay.

vonitsanet

2004-05-14 16:46

reporter   ~0006265

Completely Useless..

syzop

2004-05-16 21:44

administrator   ~0006281

Hmm implementing this is kinda ugly.. do you guys think it's worth it? [blocking of non-infected users except opers] Feedback from others is also welcome.

w00t

2004-05-16 22:18

reporter   ~0006282

Ugly it may be, but I still call it potentially useful. Opers are, as a general rule trustworthy people. They can be relied on to do the right thing, as well as offering help and advice to others (the shepherd of the flock, so to speak).

Users, on the other hand, are the bane of the technological world.

I am for both ways. As a coder, I sympathise with syzop if you have to implement this, but I think it would be useful.

syzop

2004-05-17 20:27

administrator   ~0006307

Ok, will do.
[if devel*/cvs gets alive again.. :p]

Let me explain " There's absolutely NO good reason why this should be changed" (since I cannot commit anything atm anyway :P):
there's 1 virus help channel, you probably want either opers or very trusted helpers in charge of running it.. Thus, if they place the channel +i or whatever they probably have a *very good* reason. It doesn't make sense to blindly override this... We don't (and won't) do this for any other setting either (deny::redirect, set::auto-join, set::oper-auto-join, etc), see also the channel alias discussion [0001686]. You may call it 'they are screwed' but if the ops in the channel decide, for whatever reason, not to accept any new infected users in the channel then that's their decision to make.

syzop

2004-05-17 20:37

administrator   ~0006308

Added in .2234.2.19.

Issue History

Date Modified Username Field Change
2004-05-12 07:05 bleepy New Issue
2004-05-12 09:43 aquanight Note Added: 0006200
2004-05-12 11:47 syzop Note Added: 0006202
2004-05-12 13:24 aquanight Note Added: 0006203
2004-05-12 20:05 w00t Note Added: 0006217
2004-05-12 21:33 syzop Note Added: 0006220
2004-05-13 01:27 w00t Note Added: 0006223
2004-05-14 16:46 vonitsanet Note Added: 0006265
2004-05-16 21:44 syzop Note Added: 0006281
2004-05-16 22:18 w00t Note Added: 0006282
2004-05-17 19:45 syzop Status new => acknowledged
2004-05-17 20:27 syzop Note Added: 0006307
2004-05-17 20:37 syzop Status acknowledged => closed
2004-05-17 20:37 syzop Note Added: 0006308