1
chenb0x
8y

Not best practice whatsoever because the box was most likely owned, but...

SSH kept defaulting back to port 22 when it wasn't supposed to. So, wrote a cronjob that checked diff between SSH config and backed up SSH config. If different, reload backup. Didn't get locked out again.

Box has of course been replaced.

Comments
  • 2
    Changing the default SSH port isn't considered to be that beneficial as it's simply security through obscurity.
  • 0
    @drRoss totally true. But at least it stops passive scanning on port 22. Targeted attack would be different of course.
Add Comment