> apt-cache search ssh http [...] sslh - ssl/ssh multiplexer http://www.rutschle.net/tech/sslh.shtml http://www.rutschle.net/tech/sslh.shtml I mean, it's

> apt-cache search ssh http [...] sslh - ssl/ssh multiplexer http://www.rutschle.net/tech/sslh.shtml 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 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.