Conversation

Notices

1. Acesabe (acesabe@mastodon.social)'s status on Sunday, 14-Oct-2018 09:53:06 UTC Acesabe

   • jartigag

   @jartigag jaja! That is one way to stop them! A few other basic things to secure any webserver: ensure you have port 22 closed on router (use port forwarding instead if you must SSH in directly), set up SSH keyed login, use OpenVPN to access your server network instead and setup fail2ban to manage all blocking, no manually adding IPs to block lists!
   https://www.raspberrypi.org/documentation/configuration/security.md

   • jartigag repeated this.
   • José Alb. / Speedy (josealberto4444@mastodon.social)'s status on Sunday, 14-Oct-2018 21:50:00 UTC José Alb. / Speedy

     in reply to

     • jartigag

     @jartigag The best page I've ever seen about hardening ssh is this one (even being written in 2015, I think it's still the best): https://stribika.github.io/2015/01/04/secure-secure-shell.html

     It taught me a lot of good practices regarding that. =)

     jartigag repeated this.