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.
6
-
9Why 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.– ZypherFeb 9, 2011 at 2:19
-
1@Zypher: Good suggestion.– OrblingFeb 9, 2011 at 2:55
-
2@Zypher: you are right, that's what I wanted to do– xiamxFeb 9, 2011 at 16:56
-
2@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.– OrblingFeb 10, 2011 at 3:03
-
1@Zypher Wow. Responses like yours ("Why do you want to do that?") make me irrationally angry. There are lots of places with open wifi (e.g. the local library) which for reasons I don't understand block ssh, which at times prevents me from doing my work which requires ssh into my various servers.– MichaelDec 28, 2015 at 21:40
|
Show 1 more comment
3 Answers
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.
