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
Asterisk jail does not protect asterisk manager interface #5703
Labels
verified
All test cases were verified successfully
Projects
Comments
stephdl
changed the title
FAIL2BAN: asterisk jail doesn'
FAIL2BAN: asterisk jail does not ban
Jan 29, 2019
stephdl
changed the title
FAIL2BAN: asterisk jail does not ban
FAIL2BAN: asterisk jail does not protect asterisk manager interface
Jan 29, 2019
stephdl
changed the title
FAIL2BAN: asterisk jail does not protect asterisk manager interface
Asterisk jail does not protect asterisk manager interface
Jan 29, 2019
log file for QA: https://gist.github.com/25a6f3dd28dec4db426d273480bb9e8e |
stephdl
added a commit
to NethServer/nethserver-fail2ban
that referenced
this issue
Jan 31, 2019
QA
|
Verified. |
Stell0
added
verified
All test cases were verified successfully
and removed
testing
Packages are available from testing repositories
labels
Feb 7, 2019
released as update |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
asterisk jail does not ban for the asterisk manager interface (AMI).
You can find the log file at https://pastebin.com/GhLSqt4e
Expected behavior
I expect the regex catch the attacker
Actual behavior
the attacker is not banned because the official filter from upstream is not done to match this regex
Components
nethserver-fail2ban
See also
https://community.nethserver.org/t/fail2ban-jail-properties/11831
thank to @Stell0 and Laylow
The text was updated successfully, but these errors were encountered: