View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001806 | unreal | ircd | public | 2004-05-11 04:26 | 2004-11-15 17:22 |
| Reporter | GouraudShading | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2 | ||||
| Summary | 0001806: nick in TKLs | ||||
| Description | Why can't we specify nick!user@host mask in the TKLs? It was a good solution for the lamers. I added for example this gline: /gline bastard!*@* But this causes this time 2 error msgs: 1. Cannot have ! in masks. 2. Too broad mask I know You want to prevent, that admins ban the entire network. But using the nick!user@host mask again would be nice. With a bastard!*@*.provider.hu mask can I ban a lama, and I think, that he is not going to find out, when he changes his nick, then he can reconnect. | ||||
| 3rd party modules | |||||
|
|
You can not G:Line NICKNAMES or IDENTS.. You can gline only HOSTNAMES.. If you want to ban an entire top-level domain name or an ident you can add K-lines on your unrealircd.conf file and if you want to ban nickanmes you can use Q:lines... |
|
|
Iirc you can "/gline nick ..." and unreal will replace nick with hostmask. But it won't change anything, you can't gline nicks. |
|
|
vonitsanet: Yes, I know, but when somebody Q:lined, then mIRC changes his nickname (to the alternate nick) and he can connect. I want that, when somebody connects with a specified nick, the server immediately close the connection with the specified reason. Earlier (in either beta releases) I could also K:line/G:line/Z:line somebody by his nickname, for example so: /kline Freddy!*@*.hu Go away! And this was useful for me, cos the lamers didn't find out, that he should changes their nick. And nowdays also connect people with varying host, and I can ban them only when I ban the entire provider, but that would be a big sacrifice, cos more people connect from that provider. Now do You understand my real problem? Cnils: Yes, I know also this. But when You read my notes once more, You can see my problem is other... |
|
|
Reason i see why you cant ban nicknames is becoz its impossible to stop them and theres a high chance that u hit people who arnt the target. example: New users joining the network will maybe want the nickname, and they cant connect coz u have banned them, the ircd then refers to the alternative nickname, if thats unaviable, it sits and waits for them to enter a new nickname, all this is causing is a lot of work that will no effect at all. As far as i see now *after checking* use a Qline block in the IRCD to ban a nickname, Just one and why, it will then refer to the alternative nickname. |
|
|
Just about as irritating as banning a whole ISP (*cough*dalnet*cough*) |
|
|
you can't gline idents? funny, I do it often enough. albeit you have to use an /os akill to really get away with ident@*. and there's no rule saying you can't gline ident@*.annoyingfucker.isp.tld at least i've done it and had it work. tho of course, including ident in a gline or channel ban is kinda pointless when idents have no meaning in 90% of the users platforms. |
|
|
This can probably be closed now. spamfilter target user. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-05-11 04:26 | GouraudShading | New Issue | |
| 2004-05-11 05:50 | vonitsanet | Note Added: 0006158 | |
| 2004-05-11 06:23 | Cnils | Note Added: 0006159 | |
| 2004-05-11 11:01 | GouraudShading | Note Added: 0006160 | |
| 2004-05-12 15:43 | White_Magic | Note Added: 0006209 | |
| 2004-05-12 19:36 | w00t | Note Added: 0006214 | |
| 2004-05-22 18:24 | tabrisnet | Note Added: 0006376 | |
| 2004-11-15 00:26 | tabrisnet | Note Added: 0008326 | |
| 2004-11-15 17:22 | syzop | Status | new => closed |
