Re:Show HN: Run SSH and HTTP(S) on the same port
by petercooper on Wednesday January 21, 2015 @04:02PM
(#8925747)
I wonder how far you could take this in terms of protocols. I can't think of a good use case yet, but is it at least technically possible to detect and quickly proxy away most common protocols?
[ Parent
| on HN ]
Re:Show HN: Run SSH and HTTP(S) on the same port
by fluidcruft on Wednesday January 21, 2015 @04:32PM
(#8925903)
sslh [1] (which is packaged and included in may linux and BSD distributions) has grown to support HTTP, SSL, SSH, OpenVPN, tinc, XMPP from the same port. It claims it can be extended to filter anything that can match with a regex.
What I find lacking lately is I've mostly wanted to extend the forwarding/routing of ssh connections based on username (or better by identity) to different VMs or hosts, but I have no idea how to achieve that at the moment (without creating dummy users on the sshd server).
Re:Show HN: Run SSH and HTTP(S) on the same port
by tombrossman on Wednesday January 21, 2015 @05:46PM
(#8926320)
I had a herp derp moment recently after installing OpenVPN then discovering that Nginx refused to restart because port 443 was 'bound by another process' or something like that. This looks like a pretty easy workaround.
Re:Show HN: Run SSH and HTTP(S) on the same port
by iancarroll on Wednesday January 21, 2015 @07:04PM
(#8926658)
Do note that 443 is typically the web interface for OpenVPN, not the actual VPN port.
Re:Show HN: Run SSH and HTTP(S) on the same port
by tombrossman on Thursday January 22, 2015 @02:46AM
(#8928032)
I didn't have an IPTables rule allowing the VPN traffic (UDP port 1194) and so OpenVPN falls back to using 443, which triggered the problem. I looked at the workaround and decided not to bother as I didn't really need a VPN, I was intending to use the machine as an Nginx server only.