View Issue Details

IDProjectCategoryView StatusLast Update
0001815unrealircdpublic2004-05-14 15:00
ReporterSpecial_ Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionopen 
Summary0001815: Cannot ban *\*!*@*
DescriptionWhen trying to ban all nicknames with \ in them, I found that the ban does not work.
Additional Information(07:42:21) —› mode: (Special) sets (+b *\*!*@*)
(07:42:25) —› part: (Test\) ([email protected]) ()
(07:42:26) —› join: (Test\) ([email protected])
3rd party modules

Activities

syzop

2004-05-14 11:05

administrator   ~0006245

Try: +b *\\*!*@*
No, I didn't invent it :p.
It's useless for nick!user@host bans (it allows you to escape '?' and '*' but these are never allowed) but... for some extended bans it makes sense (~r [realname], ~c [channel]).

syzop

2004-05-14 11:57

administrator   ~0006249

codemastr: perhaps worth adding a 005 thingy for this? (or any other opinions?)

codemastr

2004-05-14 13:54

reporter   ~0006253

I see no reason to add a 005 numeric for this. Read RFC2812. Granted, Unreal does not claim compliance with 2812, but we do follow this part.

RFC2812 Section 2.5:
   For string matching purposes, the protocol allows the use of two
   special characters: '?' (%x3F) to match one and only one character,
   and '*' (%x2A) to match any number of any characters. These two
   characters can be escaped using the character '\' (%x5C).

That clearly says escaping is allowed, and that we are handling the maskes he pasted correctly. So I don't see any reason to add this to 005.

syzop

2004-05-14 14:10

administrator   ~0006254

Ok, looked a bit more into it... \ does indeed not always have to be escaped to \\, coz +b Blah\!*@* will just ban 'Blah\'.
What I ment was that there's no way to tell if \ should be escaped to \\ in those special cases, like on unreal yes.. on [recent] bahamut/hybrid no.. etc.. (eg.. 30 clones join with Clone\1, Clone\2, etc.. then +b Clone\\*!*@* should be used and not Clone\*!*@*). Now whatever a RFC says.. it's confusing for clients/users.

Anyway, as said earlier, I thought it affected more, now I see it's just in a few cases so perhaps it's not worth adding a token then.

On a sidenote, I didn't say I was against escaping, I even said it makes sense for some extended ban types :P.

Issue History

Date Modified Username Field Change
2004-05-14 09:47 Special_ New Issue
2004-05-14 11:05 syzop Note Added: 0006245
2004-05-14 11:57 syzop Note Added: 0006249
2004-05-14 13:54 codemastr Note Added: 0006253
2004-05-14 14:10 syzop Note Added: 0006254
2004-05-14 15:00 syzop Status new => closed