=== The problem ===
 
=== The problem ===
   −
Brute-force breakin attempts are quite frequent against an SSH server. Automated scripts try multiple combinations of username/password and sometimes changing the port to something other than 22 can't be done. Furthermore, scouring your log files yourself is not only time consuming, but can be difficult too.<br/>
+
Brute-force breakin attempts are quite frequent against an SSH server. Automated scripts try multiple combinations of username/password and sometimes changing the port to something other than 22 can't be done. Furthermore, scouring your log files yourself is not only time consuming, but can be difficult too.
<br/>
+
 
 
{{Fail2ban}} attempts to aleviate these issues by providing an automated way of not only identifying possible break-in attempts, but acting upon them quickly and easily in a user-definable manor.
 
{{Fail2ban}} attempts to aleviate these issues by providing an automated way of not only identifying possible break-in attempts, but acting upon them quickly and easily in a user-definable manor.
    
=== The solution ===
 
=== The solution ===
   −
Log files contain interesting information, especially about failed logins. This information can be used to ban an offensive host. This is exactly what {{Fail2ban}} does. It scans log files and detect patterns which correspond to possible breakin attempts and then performs actions. Most of the time, it consists of adding a new rule in a firewall chain.
+
Log files contain interesting information, especially about failed logins. This information can be used to ban an offensive host. This is exactly what {{Fail2ban}} does. It scans log files and detect patterns which correspond to possible breakin attempts and then performs actions. Most of the time, it consists of adding a new rule in a firewall chain and sending an e-mail notification to the system administrator.
   Exception encountered, of type "Error"