View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005598||unreal||ircd||public||2020-03-24 20:39||2022-06-01 09:48|
|Platform||Unix||OS||Ubuntu||OS Version||18.04 LTS|
|Summary||0005598: Add websocket yes/no option to security-group|
|Description||I have a KiwiIRC instance that uses websockets to connect to my server and that way eliminate the need to use the KiwiIRC gateway.|
When I was using the gateway I needed to use a webirc block which worked fine.
The problem is that websockets are direct connection and therefore there's no need for webirc, which triggers my antirandom module threshold.
I'd like to know if it's possible and feasible in any way to also exempt websockets from antirandom checking.
|Tags||No tags attached.|
|3rd party modules|
I have renamed this request from "Extend antirandom module to also expect websockets connections" to "Add websocket yes/no option to security-group". Which is basically what the request would be now that we have the security group / mask item stuff in mid-2022.
I can look at it post-6.0.4. We'll see.
Related but also slightly off-topic:
Usually KiwiIRC and other trigger antirandom because they include the IP address in hexadecimal somewhere, such as the ident. If that is the case then I recommend you to disable that option. Then antirandom won't be triggered and your users also have better privacy.
Otherwise I am kinda wondering why KiwiIRC would trigger antirandom, or do people just type hfsdlhsfdklhsfd for their realname or something? :D
|2020-03-24 20:39||PeGaSuS||New Issue|
|2022-06-01 09:46||syzop||Summary||Extend antirandom module to also expect websockets connections => Add websocket yes/no option to security-group|
|2022-06-01 09:46||syzop||Note Added: 0022547|
|2022-06-01 09:46||syzop||Status||new => acknowledged|
|2022-06-01 09:48||syzop||Note Added: 0022548|