Sergey G. Brester

However (and probably especially important due to #3782 / #3785), currently I don't know better option than: ```ini journalmatch = _SYSTEMD_UNIT=sshd.service + _SYSTEMD_UNIT=ssh.service + _COMM=sshd + _COMM=sshd-session ``` The maintainer...

Reverted back in master branch (c769046a1f729880cc53efdff4b52ac96010752f) and fixed for debian now (8902a2b884c4912d24221f3eda272c5de7bb0978). Thus close.

See https://github.com/mcmilk/7-Zip-zstd/issues/377#issuecomment-2547417324

Weird. I cannot reproduce it. > Looks like a UTF character issue to me. Looks indeed like an ANSI encoding (unicode chars replaced by `?`), > I think this is...

And you get the same error, I guess?.. The question is if one does it from built script does it behaves the same way (everything is utf-8)... Because the issue...

Hmm... take a closer look to the test, it is not about streams etc... It seems that this line doesn't work for some reason: https://github.com/fail2ban/fail2ban/blob/6fce23e7baa484c7d1f9b0c9a11986f3916c41dd/fail2ban/tests/clientbeautifiertestcase.py#L188 This shall basically protect against...

OMG, it looks indeed like encoded by `backslashreplace`: ``` $ python3 -c 'print("\u2551", ["\u2551".encode("ascii",t).decode("utf-8") for t in ["replace","backslashreplace"]])' ║ ['?', '\\u2551'] ```

No, more interesting is the result of: ``` $ cd $fail2ban_source_folder $ PYTHONPATH=. python3 -c 'from fail2ban.client.beautifier import Beautifier; b = Beautifier(); b.setInputCmd(["stats"]); print(b.beautify({"ssh": ["systemd", (3, 6), (12, 24)]}));' ║...

OK, thx for tests... Never mind, ab9d41e5309b417a3c7a84fa8f03cf4f93831f1b must fix this: it just forbids the usage of unicode chars in stats table in the test suite, the table is asciified now...

Since it seems only a first authentication 401th response (handshake?), please provide few messages from this IP. Also if possible a successful attempt (I guess first invoke without a user...