Is it possible by anyway (maybe with inetd) to make 443 port serve both as sshd and as httpd SSL? Perhaps by analysing the request, if request is "CONNECT", then let httpd handle the connection; if request is ssh initialization, then let sshd handle it.
closed as off topic by Zypher Feb 9 '11 at 17:56
Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here. If this question can be reworded to fit the rules in the help center, please edit the question.
No. When an SSH client connects, the server sends an announcement. When HTTP SSL connects the server waits for the client to start the SSL handshake (ClientHello). They're mutually exclusive ways to start the protocols.
You could conceivably write a program to sit on the port, sniff the packets coming in and act as a proxy forward to the sshd and httpd servers. I can not think of any existing software that would handle that directly and transparently.
Bit like those automatic fax/phone switchers.
You could write a program to do what you suggest (analyze the incoming traffic and send it to httpd or sshd), but I don't of any existing project.