Hacker News new | past | comments | ask | show | jobs | submit login

> It’s fine that people know you changed your SSH port. But now they have to scan all the ports and find the new one.

I haven't seen a single case where the new port is not 2222.




It's been a while, but back when I did full-time sysadmin, I used a port-knocking daemon that picked a random port > 1024 (with carve-outs for some known ports) and sent that port # to my pager.

As you suggest, though, the port-knocking daemon itself ran on port 2222.


I haven't seen a case where the port is 2222.

And I've seen a few cases because I helped quite a few people with firewalld/SELinux issues related to changing the SSH port.


How many cases set up by how many operators have you actually seen?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: