Installation

SSHForwarding must be installed to the "Phone memory" and not to a memory card. This should be fixed with a future release.

Note that this release is signed using a "built in self-signed certificate". You will have to be able to install non signed sis files or be able to avoid certificate verification to proceed. A properly signed sis file will be provided once the expense of creating such a distribution can be met. 

To see if you can install non signed sis files, open the Tools/App mgr./ (options / settings ) and see if software installation = All.

During installation of the sis file a dialog "Component 'Symbian OS Pipe' missing" may appear. This is harmless and installation should be able to proceed fine.

Usage 

To use SSHForwarding you will have to copy an SSH identity file to your mobile device. To generate and setup identity files for SSHForwarding to login to a remote OpenSSH server see this this page.

The identity file should be in OpenSSH format. By default SSHForwarding will look for this file in C:\SSH\IDENTITY and C:\SSH\IDENTITY.pub. If you are copying these files to the phone via bluetooth then be sure that you can find them in C:\SSH with the file browser on the phone. Under Linux the root of the C: drive on the phone shows up as C:/Data when viewing with bluetooth.

It is best to test SSHForwarding in a friendly and fast environment first to make sure you can make a connection to your server.

Go to messaging, Options/Settings, E-mail, Select your default mailbox (the last item in the list on an e61), Connection settings.

For both Incoming and Outgoing e-mail set the mail server to 127.0.0.1 and your email tunneling setup should be complete.

Before you open your mail box and attempt to connect to it, go into your installed software "installations" and run SSHForwarding. Once you have a successful connection to the server a dialog is displayed in SSHForwarding. You need to leave SSHForwarding running to keep the packet forwarding operational. Select the application switch button to place SSHForwarding into the background and open your mailbox.

Note that the default email application is quite slow by itself and the additional overhead of SSH encryption for the forwarding will make things a little slower. 

Advanced Usage ssh_config 

As of version 1.31 of sshforwarding, you can use a ssh_config file to setup multiple custom port forwardings and many other options.

Not all the options in the man page will work with sshforwarding. In particular, sshforwarding forces things like no tty to be on as it can not handle terminal connections. Options that are outside the ones related to port forwarding are less likely to work. Some options that have been tested are: Hostname, User, Port, LocalForward.  Things like Cipher and Ciphers are best left alone as sshforwarding does not implement a great selection of ciphers as yet.

The ssh_config file allows forward and reverse port forwarding mappings to be setup, with multiple of each one per connection.

The ssh_config file needs to be in C:\SSH along with your identity file etc. The filename is ssh_config.txt so that you should be able to see and edit it with an on mobile text editor if the need to create custom configs while mobile arises.

To kickstart adoption, the below is a host specification that will connect remote ports on the example.com domain. Note that I set
 the Host to Q so that when I select to "connect with ssh_config" in sshforwarding I can select the host with a single character.

Host Q
        Hostname example.com
        User e61tester
        Port 99
        LocalForward 993 localhost:993
        LocalForward 110 localhost:110
        LocalForward 25  localhost:25

This should also let you tell sshforwarding where to connect to on the remote machine instead of localhost.