SSH:Konfigurasi dengan Fail2ban: Difference between revisions
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
*Begin by creating a new file within the same directory called jail.local. You can then add the necessary security configurations for the sshd jail. | *Begin by creating a new file within the same directory called jail.local. You can then add the necessary security configurations for the sshd jail. | ||
vim /etc/fail2ban/jail.local | |||
*You can explore the options that Fail2Ban provides to customize the security and blocking of the SSH service. | *You can explore the options that Fail2Ban provides to customize the security and blocking of the SSH service. | ||
| Line 30: | Line 31: | ||
*With the information in table above you can create the jail.local configuration for OpenSSH server (sshd). Once you have entered the configuration options, the values used in this guide example are listed in the sample file below. | *With the information in table above you can create the jail.local configuration for OpenSSH server (sshd). Once you have entered the configuration options, the values used in this guide example are listed in the sample file below. | ||
[sshd] | [sshd] | ||
enabled = true | enabled = true | ||
| Line 42: | Line 42: | ||
*After you have specified the configuration options and their respective values, save the file and restart the Fail2Ban service with the following command: | *After you have specified the configuration options and their respective values, save the file and restart the Fail2Ban service with the following command: | ||
sudo systemctl restart fail2ban.service | |||
*After restarting the OpenSSH server service, Fail2Ban uses this new configuration and the jail for the sshd service is activated and runs. | *After restarting the OpenSSH server service, Fail2Ban uses this new configuration and the jail for the sshd service is activated and runs. | ||
*You can now test this functionality by re-enabling PasswordAuthentication in the OpenSSH Configuration file found in <code>/etc/ssh/sshd_config</code>. Do this by changing the value from no to yes using the text editor of your choice. Make sure these lines are uncommented. | *You can now test this functionality by re-enabling PasswordAuthentication in the OpenSSH Configuration file found in <code>/etc/ssh/sshd_config</code>. Do this by changing the value from no to yes using the text editor of your choice. Make sure these lines are uncommented. | ||
#To disable tunneled clear text passwords, change to no here! | |||
PasswordAuthentication yes | PasswordAuthentication yes | ||
PermitEmptyPasswords no | PermitEmptyPasswords no | ||
| Line 55: | Line 55: | ||
==Source== | ==Source== | ||
*[https:// | *[https://www.linode.com/docs/guides/how-to-use-fail2ban-for-ssh-brute-force-protection/ linode.com] | ||
[[Category:Tutorial]] | [[Category:Tutorial]] | ||
[[Category:Server]] | [[Category:Server]] | ||
[[Category:Security]] | [[Category:Security]] | ||