You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, each decision being fed to the custom-bouncer leads to an execution of the script. With the ever-growing (yay) list of decisions in the community-blocklist, it is (and will) become an issue. We need to have something that scales best.
Allowing the user script to be fed via stdin seems to be a good alternative. Named pipe or such might be too, but would add unnecessary complexity ?
Allowing configurable batching parameters at the bouncer level (frequency and/or number of items)
Question / Things to deal with
Configurable batch windows size/time
Configurable behavior on child process crash (restart/die)
The text was updated successfully, but these errors were encountered:
Problem
Currently, each decision being fed to the custom-bouncer leads to an execution of the script. With the ever-growing (yay) list of decisions in the community-blocklist, it is (and will) become an issue. We need to have something that scales best.
cf. https://discourse.crowdsec.net/t/custom-bouncer-firewalld-questions/565
Solution
Allowing the user script to be fed via stdin seems to be a good alternative. Named pipe or such might be too, but would add unnecessary complexity ?
Allowing configurable batching parameters at the bouncer level (frequency and/or number of items)
Question / Things to deal with
The text was updated successfully, but these errors were encountered: