Re:Show HN: Run SSH and HTTP(S) on the same port
by userbinator on Thursday January 22, 2015 @10:44AM
(#8929725)
It's interesting that SSH requires the server to respond with a message upon connection, independent of whether the client sends anything - perhaps hiding the service on a different port was not a strong consideration when it was designed.
On the other hand, HTTP and SSL/TLS servers will just wait silently for the client to initiate the conversation.
I know obscurity can't replace security, but security + some obfuscation could help you a bit for not getting hacked instantly by 0-days. It's easier to setup on client side than port knocking (you just have to set the port) but it's less detectable than sshd on a random port.