View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000105 | unreal | ircd | public | 2002-03-18 23:23 | 2003-11-20 19:46 |
| Reporter | Zerwas | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2-beta7 | ||||
| Summary | 0000105: Add a way to restrict a connection | ||||
| Description | It would be nice if there were a way to restrice a connection. So that a specific IP and/or Userclass can't use /mode /nick and so on. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I was at one point going to add this but then I saw that just about every IRCd that did have it (LITTLE_ILINES) [bahamut,hybrid,(ircu?)] removed it, so I'd just like to hear what other people think about this idea... |
|
|
Afair ircu never had it, while ircd still uses it. It would be useful, though, in some cases where some clients are messy and a kline on the whole subnet/domain is not advisable. |
|
|
I think it would be a good idea to have this feature. Our "little" irc-network with up to 2 or 3 Thousand Concurrend User is sometimes visited by scriptkiddies or other users which sometimes have annoying behaviour. To set them, their bouncers or bots on a restricted connection would help in much cases. I know about the restricted conns on IRCnet and there I saw that it was a good idea to restrict conns from some dial-in Providers. (Customers of them made the network splitting) |
|
|
Or maybe to give some parameters to the SHUN command ? like: SHUN +/-{user@host} [+/-{command flags}] {time} :Reason where [command flags] would be the commands that have to be disabled (-) or enabled (+) for the given user@host Giving flags like m for modes, n for nick changing, j for join... not all the commands, just the ones that can be used to annoy other people Giving no command flag would make a normal shun /shun +*@uglyboyz.com -mn 0 :Too stupid to be real... prevents all users coming from uglyboyz.com to do modes or to change their nick... was just an idea... |
|
|
*bump* |
|
|
Bump?? *G* We have still some guys on our system that we think, it is a good idea to have a way to restrict a connection. But I think it's not easy to add this Feature? Some of these guys have very extremely annoying behaviour... At this moment we are only able to set a gline for them. but we are not able to restrict the ISP. which would quite more effective I think. Some ISP do not cooperate properly on abuse cases belonging to chatsystems... So it's something like self-defense... |
|
|
Just wondering, since we (me+codemastr) see it get's pretty messy if we implement this. How will this stop flooders/attackers? I mean, with ircnet the restricted usermode could be usefull to prevent takeovers, but these days all the (non-ircnet) networks have TS and most have chanserv etc so that's not the case anymore. I mean, the attacker can still flood (private msg, channel msg, join/part, whatever), so what does it help? |
|
|
Yes thats right. For IRCnet it is usefull, because they have no services, and implemented that to prevent many takeovers. There wasn´t any other reasons IMHO! But for networks with services it is useless I think. And many (new) networks have that. And how sysop says... attackers can still flood. So if users from, as an example, make problems from *!*@*.aol.com, you can ban them. |
|
|
Well if no one has a good reason why this should be added... |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-04-11 21:29 | syzop | Note Added: 0002274 | |
| 2003-04-13 18:20 | Rocko | Note Added: 0002304 | |
| 2003-04-13 18:28 |
|
Note Added: 0002305 | |
| 2003-04-14 04:54 |
|
Status | feedback => resolved |
| 2003-04-14 04:54 |
|
Resolution | open => no change required |
| 2003-04-14 04:54 |
|
Assigned To | => codemastr |
| 2003-11-20 19:46 | syzop | Status | resolved => closed |
