SailAutoSSH

Rating: 
0
No votes yet

SailAutoSSH is a small tool that allows to create SSH tunnels on demand. The user can configure several services that listen at the localhost for new connections made by some app and forwards them through an SSH tunnel to a remote host.

The tunnel host must be configured for public key authentification.

Source code available at https://bitbucket.org/lyro/sailautossh

Bug tracker: https://bitbucket.org/lyro/sailautossh/issues

Screenshots: 
Application versions: 
AttachmentSizeDate
sailautossh-1.0.0-1.armv7hl.rpm64.2 KB17/04/2015 - 01:23
sailautossh-1.0.1-2.armv7hl.rpm64.68 KB17/04/2015 - 13:24
sailautossh-1.1.0-1.armv7hl.rpm42.09 KB08/09/2015 - 14:26
sailautossh-1.1.1-1.armv7hl.rpm42.75 KB08/09/2015 - 16:49
sailautossh-1.1.1-2.armv7hl.rpm42.76 KB08/09/2015 - 17:01
sailautossh-1.2.0-1.armv7hl.rpm43.21 KB16/09/2016 - 22:51
sailautossh-1.3.0-1.armv7hl.rpm43.18 KB18/09/2016 - 20:22
Changelog: 

- desktop version of app

Comments

jayki's picture

Hey, thanks for you app :)
Is it possible to add the Port parameter (ssh -p), because i can't use standard port 22 here :(
would be very helpfull :)
thanks ;)

fifr's picture

Could you please check if the sailautossh daemon is running:

$ systemctl --user status sailautossh

if not, please try to start it with

$ systemctl --user start sailautossh

If this does not work, too, try to start it directly

$ sailautosshd
naytsyrhc's picture

I tried that and the service was running. On reopening the app all configured tunnels became visible. However I could not activate / establish any of them. Is there a logfile or some possibility to debug that?

fifr's picture

First you could try to restart the daemon (it could be that the one of version 1.0.0 is still running)

$ systemctl --user stop sailautossh

and then restart the gui (this should restart the daemon). However, I do not thing that this makes a difference.

There is some debug output, but I'm not sure how helpful it is (to be honest, the error reporting is not that good at the moment). The easiest way is probably to stop the daemon temporarily (as above) and then start the gui in stand-alone mode without the daemon. In the terminal run

$ sailautossh -s

Then establish the tunnel with whatever app you want and look at the console output.

You could also verify first that the ssh tunnel can be established manually. Sailautossh just executes the following command:

$ ssh -W targethost:targetport -l tunneluser tunnelhost

Execute that command in the terminal and see what happens (actually, nothing should happen, in particular you should not get any error). If sailautossh establishes a connection successfully, the command

$ ps ax | grep ssh

should show exactly the above ssh command running.

Please check if something of this helps you. If not, please let me know, then we have to investigate further ;) (and sorry for the inconvenience)

 

naytsyrhc's picture

Nice idea. I'd really love to try and use it. Unfortunately even with latest update 1.0.1-2 my entered settings are not stored and not shown in GUI. Any ideas?