View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005333||unreal||ircd||public||2019-07-18 17:39||2019-08-18 15:29|
|Target Version||Fixed in Version|
|Summary||0005333: U5: control channel characters / utf8|
|Description||As I mentioned in https://github.com/ircv3/ircv3-specifications/pull/342 it is a problem if non-utf8 characters are allowed in channel names. Regardless of websocket, some configuration/control is likely a good idea.|
At this time we don't have some kind of universal anti-look-alike system, which is what another IRCv3 effort is about..
I'm thinking of some options here like:
1. the current policy, block only ASCII <32
2. only valid utf8
3. only a-zA-Z0-9 and some characters, effectively block high ascii / block utf8
And I think the default should change from option 1 to option 2.
A more security conscious decision would be option 3, due to the lack of lookalike checking, but that's too strict for a default I think.
|Tags||No tags attached.|
|3rd party modules|