View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001418 | unreal | ircd | public | 2003-12-09 19:00 | 2004-03-12 21:34 |
| Reporter | doh | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0001418: /zline and /gzline acting like /kline and /gline | ||||
| Description | I have been unable to find any difference between /zline and /kline or /gzline and /gline.. It seems that both examples will do both IP and hostmask bans.. While this seems nice it renders one pair of them useless, also the documentation mentions /zline and /gzline as zline +-<ip> <time to ban> <reason> gzline +-<ip> <time to ban> :<reason> It makes more sence without the ident@host way in my opinion, as you could kill the client even before getting ident or hostmask | ||||
| Additional Information | /helpop mentions /kline and /zline the exactly same way, and so it does with /gzline + /gline. Either documentation should be changed, or the way it makes more sence in my opinion, change the way /zline and /gzline works | ||||
| 3rd party modules | |||||
|
|
Zlines and Klines are very different. Yes, a Kline can be used on an IP, the difference is "when" the killing is done. A Zline is executed before the user has a chance to connect no "looking up your hostname" notices, you're gone instantly. On the other hand, a Kline waits until you've fully connected to the server and then kills you. |
|
|
Why is it then possible to enter user@host at zlines? I guess the user@ part is ignored then? |
|
|
no, because the NICK command is sent... I believe before "connection" occurs. Best we do some research into the IRC protocol, eh doh? |
|
|
w00t, doh: commands /zline and /gzline add the mask you give, even if it's in user@host form (which should be just an IP address), but yes, usernames are ignored when the ircd checks clients if they are banned. And this checking is made _immediately_ when clients connect, the server even doesn't allow them to send at least a NICK command. edited on: 12-10-03 09:21 |
|
|
whoops... my bad... We check for zlines before NICK & USER are processed, correct? Klines wait till NICK, USER etc are processed then kill the bugger, correct? Sorry, my mind is whalgqlgnqlegn... need sleep... <zzzzzz> ;P |
|
|
btw, we just don't "verify" *lines.. I mean /zline *@1.2.3.4.5 also works... seems just a minor thing however, more like documentation or warning.. nothing critical... Oh and if the request was to add @host support then NO.. because zlines are in effect even before dns lookups are done. As mentioned earlier, it's done immediately on accept(). |
|
|
It could be great if there was a way to see the remote address before the accept(). Then before calling accept() you check your Z-lines and if a match, don't call accept() (instead refuse the connection). Then you get: Non-ZLined client: * Connecting to irc.mynet.net... -irc.mynet.net-- *** Looking up your hostname... (etc.) ZLined client: * Connecting to irc.mynet.net... * Unable to connect to server (Connection refused) Then the user can't tell between Z-Line and down server. |
|
|
to be honest I've no idea why this "bugreport" is still open since there's no bug.. rather someone was asking for support or something. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-12-09 19:00 | doh | New Issue | |
| 2003-12-09 21:27 |
|
Note Added: 0004269 | |
| 2003-12-09 23:10 | doh | Note Added: 0004270 | |
| 2003-12-09 23:31 | w00t | Note Added: 0004273 | |
| 2003-12-10 09:19 | AngryWolf | Note Added: 0004274 | |
| 2003-12-10 09:21 | AngryWolf | Note Edited: 0004274 | |
| 2003-12-16 02:56 | w00t | Note Added: 0004358 | |
| 2003-12-16 03:14 | syzop | Note Added: 0004359 | |
| 2004-03-12 19:11 | aquanight | Note Added: 0005447 | |
| 2004-03-12 21:34 | syzop | Status | new => closed |
| 2004-03-12 21:34 | syzop | Note Added: 0005448 |
