After about an hour of testing SSH Tunneling/Port Forwarding to no avail, I’ve discovered that loopback, or localhost to localhost, connections are “sandboxed” in Windows Store apps. Meaning that an app listening on localhost can only connect to its own services. Desktop apps cannot communicate to Metro apps through TCP/IP or UDP through localhost. In fact, the rule is so strict that you have to use a tool to temporarily and locally enable loopback exemptions for testing:
How to enable loopback and troubleshoot network isolation
So what does this have to do with SSH Tunneling/Port Forwarding? It means that the idea that you’d be able to connect to localhost:23 to tunnel telnet traffic, or localhost:8081 to proxy HTTP connections, is really not feasible in Windows Store apps at this time. Developers are able to tunnel internal components, such as an in-app browser, but Desktop apps and other Metro apps would not be able to.
If Microsoft reneges on this policy in some way that allows a Windows Store app to run as, or register, a local service then SSH Terminal Emulator will have the feature ready; however, until that time comes, I have to put the feature to rest.
I’m sorry for anyone who I may have unintentionally misled about this feature being available in a matter of time. I’m learning this framework along the way, as are many developers. I hope that this does not dissuade anyone from purchasing or using the app. In fact, I hope my honesty and frankness show you how dedicated I am to this project. I use this app just like you. This was a feature I wanted in the app, but it is not possible with the current framework Microsoft has given developers.
On a side note, check back soon for a Release 9 Preview post.
Thanks again for all your support!