Anonymous | Login | 2024-11-21 05:08 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0009051 | ClearOS | app-ssh-server - SSH Server | public | 2016-06-03 09:07 | 2016-12-16 14:04 | ||||
Reporter | dloper | ||||||||
Assigned To | user2 | ||||||||
Priority | low | Severity | feature | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 7.2.0 | ||||||||
Target Version | 7.3.0 Beta 1 | Fixed in Version | 7.3.0 Beta 1 | ||||||
Summary | 0009051: App doesn't block ssh when using non-standard port | ||||||||
Description | Fail2ban is unaware of port changes made in app-ssh-server. When configuring fail2ban or when configuring app-ssh-server, these two should be marginally aware of each other. If the port was changed to 222 then changes could be made to: port = 222 in jail.d/clearos-sshd.conf and jail.d/clearos-sshd-ddos.conf Alternately, you can block all traffic based on the hit using: banaction = iptables-allports in /etc/fail2ban/jail.conf | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Issue History | |||
Date Modified | Username | Field | Change |
2016-06-03 09:07 | dloper | New Issue | |
2016-06-13 08:23 | user2 | Status | new => confirmed |
2016-11-16 09:12 | user2 | Target Version | 7.3.0 Beta 1 => 7.3.0 Beta 1 |
2016-12-09 14:01 | user2 | Category | app-attack-detector - Attack Detector => app-ssh-server - SSH Server |
2016-12-09 14:01 | user2 | Status | confirmed => resolved |
2016-12-09 14:01 | user2 | Fixed in Version | => 7.3.0 Beta 1 |
2016-12-09 14:01 | user2 | Resolution | open => fixed |
2016-12-09 14:01 | user2 | Assigned To | => user2 |
2016-12-16 14:04 | user2 | Status | resolved => closed |