On Fri, Jul 31, 2015 at 5:17 PM, Yaroslav Halchenko <li...@onerussian.com> wrote:
> why not to just push it into public location and share a link? ;) > The list will get a link next week. Polishing means that it will be something better than a proof-of-concept, and actually a good initial base for contributions. > I would also second reusing fail2ban mechanisms instead of relying on > parsing its log file (we know how things could go wrong with > parsing/monitoring ;) ). Especially since actions could be defined in > pure python (see eg config/action.d/*py) and that would avoid "small > scripts" issue, would guarantee staying coherent and tested within > fail2ban. > I have detailed my reasons to avoid creating an action in a different reply. In any case, as the fail2ban-zmq-tools package I am creating is a set of three different modules, it would be more than extremely simple to ignore the Monitor module, and just add the necessary code to send zmq messages to the Publisher module as f2b actions, with pure python code. thanks yarosla :D I appreciate your interest and insight!
------------------------------------------------------------------------------
_______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
