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

I'm looking to move ssh off port 22, and had tried out sslh;

sslh ssl/ssh multiplexer - accepts HTTPS, SSH, OpenVPN, tinc and XMPP connections on the same port. This makes it possible to connect to any of these servers on port 443 (e.g. from inside a corporate firewall, which almost never block port 443) while still serving HTTPS on that port.

However those services then see traffic originate from 127.0.0.1, instead of the external host making the request - for authentication/logging/identification purposes I've had to disable sslh.

Recommendations for alternative options?

Should I investigate using stunnel to proxy ssh through nginx?

link|improve this question
If you are using a tunnel or proxy then the source IP address will always be the endpoint rather than the origin. It has be this way for reply packets to get sent to the endpoint rather than the origin. – Paul Jan 18 at 2:15
yes but with proxying you can add headers, to trace the source ip – Thermionix Jan 18 at 2:56
For web services certainly. What about vpn and ssh and tinc and xmpp? – Paul Jan 18 at 3:12
I was curious if this was possible on a lower layer than the Application Layer – Thermionix Jan 23 at 0:25
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.