News for hackers. Stuff that matters.
Re:Show HN: Run SSH and HTTP(S) on the same port by AceJohnny2 on Wednesday January 21, 2015 @04:42PM (#8925967)

  > apt-cache search ssh http
  [...]
  sslh - ssl/ssh multiplexer
http://www.rutschle.net/tech/sslh.shtml

I mean, it's cool that you got the exercise of implementing this in Go and all, but I don't see what's new and interesting about it.

(and another implementation in Perl almost 4 years ago: https://news.ycombinator.com/item?id=2395787)

Edit: oh whoops, didn't get to OP's "Why not sslh" section :\ "The result is useful in its own right through use of Go's interfaces for protocol matching (making adding new protocols trivial), and lightweight goroutines (instead of forking, which is more CPU intensive under load)."

Well alright, the first point I'll concede, though I'm wary of the "reinvented wheel" scent, the second point I'm even more uncomfortable with as I think it makes wild assumptions of the kind of environment this tool could be useful in.

Re:Show HN: Run SSH and HTTP(S) on the same port by bmn_ on Thursday January 22, 2015 @09:28AM (#8929251)
> and another implementation in Perl

[sslh in Net-Proxy](https://metacpan.org/pod/release/BOOK/Net-Proxy-0.03/script/...) predates that even longer - first release in 2006.

Re:Show HN: Run SSH and HTTP(S) on the same port by Hello71 on Thursday January 22, 2015 @08:31AM (#8929007)
The latter part makes me question whether the author read sslh's readme; it clearly notes that there is sslh-fork and sslh-select. If I recall correctly, upstream defaults to sslh-fork because it has lower idle overhead, and is arguably more reliable due to use of less code.
Re:Show HN: Run SSH and HTTP(S) on the same port by zeendo on Thursday January 22, 2015 @07:34AM (#8928811)
"wild assumptions" ? That's a bit hyperbolic, no?