up vote 3 down vote favorite
share [g+] share [fb]

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.

link|improve this question
9  
Why in the world would you want to do this? The only reason I can think of for something like this would be to go around company firewall policies. – Zypher♦ Feb 9 '11 at 2:19
@Zypher: Good suggestion. – Orbling Feb 9 '11 at 2:55
1  
@Zypher: you are right, that's what I wanted to do – xiamx Feb 9 '11 at 16:56
@Zypher: I do not see how this is off-topic, it may be undesirable behaviour, but it is still server software setup, it is not "off-topic". Just unpleasant. – Orbling Feb 10 '11 at 3:03
feedback

closed as off topic by Zypher♦ Feb 9 '11 at 17:56

Questions on Server Fault are expected to generally relate to servers, networking, or desktop infrastructure, within the scope defined in the faq.

3 Answers

up vote 5 down vote

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.

link|improve this answer
feedback
up vote 1 down vote

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.

link|improve this answer
feedback
up vote 0 down vote

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.

link|improve this answer
feedback

Not the answer you're looking for? Browse other questions tagged or ask your own question.