MKmkj·Jan 22, 2015
It doesn't appear to set tcp nodelay, as with most of these forwarders. https://github.com/stealth/sshttp does it at the kernel level, much better.
In Show HN: Run SSH and HTTP(S) on the same portstealth
sshttp
C++2012–2015
stealth / sshttp
sshttp
SSH/HTTP(S) multiplexer. Run a webserver and a sshd on the same port w/o changes.
4Distinct people
4Mentions
0Explicit recommenders
894GitHub stars
What to know before exploring
What it is
SSH/HTTP(S) multiplexer. Run a webserver and a sshd on the same port w/o changes.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:24:10 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year4 dated mentions
Observed mentions: 2012-02-10 11:32:40 UTC to 2015-01-22 02:37:03 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sources> above port 1024 malware...
Im using this https://github.com/stealth/sshttp to run it on port 443.
The other port it actually runs on is firewalled off from outside.
In SSH Brute Force – The 10 Year Old Attack That Still PersistsIf they're proxying HTTP traffic usually they'll block SSH and other protocols. To work around this use an HTTPS/SSH multiplexer[1][2][3] or a simple reverse proxy to accept HTTP[S] connections and connect them to an SSH server on the backend. For the ssh client use a ProxyCommand tunneling app[4][5][6] to turn an HTTP[S] proxy request into a two-way socket, and you have an SSH connection over HTTP proxies.
[1] http://www.rutschle.net/tech/sslh.shtml
[2] http://www.pond-weed.com/multiplex/
[3] https://github.com/stealth/sshttp
[4] http://zwitterion.org/software/ssh-https-tunnel/ssh-https-tu...
[5] http://proxytunnel.sourceforge.net/
[6] http://www.agroman.net/corkscrew/
In Websockets 101Realise ALL encryption handshake are blocked but Maybe this might work.
https://github.com/stealth/sshttp
You do need a server on the 'outside' though. (oh bugger, github uses https)
In Iran Shuts Down Major Websites and Https Protocol