News for hackers. Stuff that matters.
Re:Persistant SSH Threats? by MrLabCoat on Thursday January 23, 2020 @01:32PM (#22130250)
I do something similar but added a knock daemon and changed the default ssh port 22 to something else.

So far I haven’t had any issues, fail2ban works, and it seems safe.

I do have my home IP added to the whitelist and others set to drop.

I was told in a networking class this is the second best way to protect ssh other than not running ssh.

Any thoughts on this setup as well? Maybe oversights that I’m not seeing?

There are no comments on this comment yet.