View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006095||unreal||module api||public||2022-05-05 15:56||2022-05-14 19:45|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Fixed in Version||6.0.4-rc1|
|Summary||0006095: antirandom module|
|Description||In future if the author of antirandom module can add 1 option for secure connection as exempt it wil be helpfull, ty in advance|
|Tags||No tags attached.|
|3rd party modules|
||As I said in channel, personally I would be in favour of making both of these options into "match" criteria, separate from mask, in the "except ban" blocks, allowing you to except clients that match those criteria from antirandom.|
I strongly advise against the
except-secure yes;because nowadays any bot/proxy/vpn/etc is/are able to use TLS connections and that would defeat the purpose of the antirandom module.
Meanwhile, if you really want to exempt ALL TLS users from the antirandom module, you can use an E-Line, like the following:
ELINE ~G:tls-users r 0 Antirandom TLS exemption.
Once again, as already said above, I don't advise you to do so since it will decrease your network security.
UnrealIRCd 6.0.4 now has the same options in mask/match/except as in security-group. I added/transformed: antirandom, antimixedutf8, connthrottle and restrict-commands to accept these too.
For antirandom in particular, see the example block: https://github.com/unrealircd/unrealircd/blob/unreal60_dev/doc/conf/modules.optional.conf#L112-L126
You can use all features of https://www.unrealircd.org/docs/Mask_item there.
|2022-05-05 15:56||Breaking||New Issue|
|2022-05-05 16:03||Jobe||Note Added: 0022469|
|2022-05-05 17:41||PeGaSuS||Note Added: 0022470|
|2022-05-14 19:45||syzop||Assigned To||=> syzop|
|2022-05-14 19:45||syzop||Status||new => resolved|
|2022-05-14 19:45||syzop||Resolution||open => fixed|
|2022-05-14 19:45||syzop||Fixed in Version||=> 6.0.4-rc1|
|2022-05-14 19:45||syzop||Note Added: 0022484|