I'm thinking about setting up SSLH on my personal server. >From http://freecode.com/projects/sslh: ----
> sslh 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 blocks port 443) while still serving HTTPS on that port. In short summary (and to my limited understanding), SSLH works by forwarding the connection from the sslh daemon to either the ssh server or the web-server (among other options). This means all SSL connections will ultimately appear to be connecting to apache/web2py via 127.0.0.1. Are there any security concerns with this? Should I disable admin and appadmin completely? How are session cookies affected? Would any other functionality be affected?
