View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005522||unreal||ircd||public||2020-01-05 08:00||2020-02-17 22:45|
|Platform||Unix||OS||Ubuntu||OS Version||18.04 LTS|
|Target Version||Fixed in Version|
|Summary||0005522: add "*" to /ELINE command to cover all available bantypea|
|Description||As the title explains, would be nice to have a "*" to create an /ELINE that would cover all available bantypes, instead the need to specify all bantypes when wanting to exempt an IP from all of them.|
So, something like: /ELINE *@host * 0 reason
|Tags||No tags attached.|
|3rd party modules|
The main problem is: what is "all" and do people really expect "all":
Sure, one can make * include really everything, but then it also bypasses throttle, qline restrictions and even maxperip restrictions. This is likely not always what the user expects.
So one hand users may expect to exempt only from *LINEs and Spamfilters, and on the other hand it is understandable that other users may expect really to include everything, including maxperip.
I avoided that issue by simply not offering the functionality. That way you have to choose the types to exempt explicitly.
In the configuration file "except ban" there is a type "all" and it is already a potential cause of trouble... it does not include qline bypassing but does include maxperip and such.. that is bad I think.
IMHO, if we use "*" as to exempt a specific IP from all the possible protection measures, that's probably because we do have a strong reason.
I'll name a few that makes sense to me:
- Exempt network BNC services (same IP for all users)
- Exempt personal bots (entertainment bots, channel management bots, etc)
- Exempt a specific trusted ISP/BNC/Etc provider
Those are just some thoughts that came to my mind. Feel free to close this "issue" if you think that still the best option is to add specific types in the ELINE command