Sergey G. Brester

> It still bans IP after successful connection Then your successful connection seems to log "CTRL read failed" for some reason. As already said, I don't see at the moment...

I'll try to adapt it for current dev branch (e. g. check against my own subnet implementation)

> the binary data is sometimes a few characters, sometimes contains multiple lines with carriage returns, etc. Oops. If it is really so (the data is written really unescaped to...

BTW... it looks indeed like it will be written unescaped at the moment: https://github.com/sebres/nginx/blob/1b6e3dcf16afc941c6d82c941d965760779605b3/src/core/ngx_proxy_protocol.c#L142-L143

Thx! No, transmitter is only for commands supplied to the server, which `help` should not be (at least at the moment fail2ban server does not provide special command for help)....

> so it good idea to fix this line to support prefix elements? conditionally... I would not do it by default right now (due to possible performance losses) at least...

just for the record, to link to #927

\ *Why must devs continuously change the log format, moreover activate structured logging by default...* \ But, OK... ```ini [Definition] datepattern = ^\{"t":\{"\$date":"%%Y-%%m-%%dT%%H:%%M:%%S\.%%f%%z"}\s*,\s* _groupre = (?:"(?!(?:msg|attr|client|remote)\b)\w+":(?:"[^"]+"|\w+)\s*[,\}]\s*) failregex = ^%(_groupre)s*"msg":"Authentication failed"\s*,\s*%(_groupre)s*"attr"\s*:\s*\{%(_groupre)s*"(?:client|remote)":":\d+"...

Is it something like: ```bash fail2ban-regex --out-action 'my-action[prm1="val1",...]' $log $filter ``` Or: ```bash fail2ban-regex --out-tags $log $filter ``` Could you provide an example, just for better understanding, what do you...

Although it would be relative easy to implement for some script-actions (but no way for pythonic actions). Just some tags are depended on the init-arguments specified in `jail.conf` resp. distribution-related...