Skip to content

Conversation

ppom0
Copy link
Contributor

@ppom0 ppom0 commented Aug 12, 2025

The problem

fail2ban

Solution

reaction

introduction to problem & solution

PR Status

Very much draft

How to test

Absolutely no migration ready for now, I'm just opening this to let us know that it's a WIP.

@ppom0 ppom0 changed the title reaction over fail2ban replace fail2ban by reaction Aug 12, 2025
@alexAubin alexAubin changed the title replace fail2ban by reaction WIP: replace fail2ban by reaction Aug 12, 2025
@Thovi98
Copy link
Contributor

Thovi98 commented Aug 13, 2025

This seems very nice, thanks!
I’ve just a little observation: fail2ban has a great community, while reaction seems to be only maintained by you (If I’m not mistaken). What is the reliability of reaction being maintained if you decide to stop working on it for example? :)

@ppom0
Copy link
Contributor Author

ppom0 commented Sep 6, 2025

That's indeed a good question @Thovi98 😅

A major difference between reaction and fail2ban is that the latter provides lots of default configuration, which needs maintenance. fail2ban also does more things, with its own configuration system, datetime parsing, etc, that reaction's core doesn't have to handle.

According to me, reaction's core is mostly feature complete now, so it could be used with no (or little) need for further development.

Future development will mostly be on a plugin system and on its plugins. They'll need more maintenance, because some will do more complex things that reaction's core (clustering for example). But they'll be opt-in.

I also hope that those additional features will make reaction more attractive and bring some new contributors, but that's something I can't assure you 😉

@zamentur
Copy link
Member

Related to YunoHost/issues#2423

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants