Sergey G. Brester

> my sqlite DB for fail2ban did grow over the years to 300MB Well, since fail2ban deletes the old entries periodically (by `dbpurgeage` that is typically larger than a day),...

I don't think auto-vacuuming is good idea - when the auto-vacuum mode is 1 (means "full"), the pages are moved and the database file is truncated **at every** transaction commit....

7c99a39e6dc40367b4bbd3173f3db9dcc799cc97 seems to fix the GHA flows now (completely different issue), so can be cherry-picked to main branch as it is (or I could make a separate PR if necessary).

Ping. Is this repository alive?

> The PR #147 will help fix the GH Action headache for this PR. Hmm... There is basically no problem to fix "for this PR" - as you can see...

I'm unsure it is good idea, because fail2ban is not only python package, but also a service, so its installation expects more than an installation via pip... moreover normally it'd...

If I try to configure a pending publisher for a project on pypi, I get a (very informative) error "This project name isn't allowed"...  A manual test to start...

Just as a thought: possibly pass2allow would be good enough as alternative white-listing for you in this case, for realization see e. g. jail [pass2allow-ftp](https://github.com/fail2ban/fail2ban/blob/0.9/config/jail.conf#L819)

I don't think the enhancement like this will provide a great benefits for fail2ban: - option `ignorecommand` can be used to check the IP should be ignored (and if gh-2176...

So why the `ignorecommand` would not be suitable in your case?