Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Being able to feed decisions to the script via stdin #29

Closed
2 tasks
buixor opened this issue Jan 24, 2022 · 0 comments · Fixed by #36
Closed
2 tasks

Being able to feed decisions to the script via stdin #29

buixor opened this issue Jan 24, 2022 · 0 comments · Fixed by #36

Comments

@buixor
Copy link
Contributor

buixor commented Jan 24, 2022

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

  • Configurable batch windows size/time
  • Configurable behavior on child process crash (restart/die)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant