New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backslash in logs are interpreted #1165
Comments
Agree. Which mail-action you have used here? Can you provide a config excerpt resp. better an output of |
|
Yes, it's a execution inside execution. |
I'd prefer to view the same lines in the email as in the log. |
Could a simple |
I believe this and similar other are already fixed (I cannot reproduce it anymore). |
@sebres So for example
in the email? |
0.10? (or 0.9) |
I am not able to run 0.10 because it is not packaged for Debian |
Wiki - How to test newer fail2ban version resp. use fail2ban standalone instance Is meant parallel to your running stock fail2ban, without installation. Just copy your customization there as described and disable banning action (or replace it with "dummy" - we've such action;) there to prevent dual bans (from test instance also)... |
Thank you. |
I think it is a security matter.
Log:
Email:
Backslashes should be escaped in log lines.
The text was updated successfully, but these errors were encountered: