jaroslawp / gstm Goto Github PK

This is a Gtk3 port of gstm, based on v1.2 available at: https://sourceforge.net/projects/gstm/

Dependencies on deprecated libgnome libraries have also been removed.

gSTM is a simple front-end to openssh, built to make managing port-forwarding tunnels a little bit easier. Usage and configuration should be fairly straightforward. Errors generated by ssh are caught and displayed, and an SSH_ASKPASS-compatible program (gAskpass) is provided for use with password authentication, if one is not already present and configured. See the openssh manual for details on SSH_ASKPASS.

Ensure your SSH connection is in good working order prior to setting up a new tunnel in gSTM. A good way of doing this is to run a quick test from a terminal first: you@prompt$ ssh -p portnumber username@host.

Note: The first connection to a new, previously-unseen ssh server that is configured for pubkey authentication will cause ssh to display the server key and prompt the user to accept it. This is not detectable by gSTM, and the tunnel will appear to be connected but hang indefinitely. To avoid this, check your ssh connection as described above.

• For Gentoo users, an ebuild is available in my layman overlay: https://github.com/dallenwilson/trolltoo

• Ubuntu users (and Mint, Debian and other related distros) can find deb packages in my launchpad ppa: https://launchpad.net/~dallen.wilson/+archive/ubuntu/ppa

• ArchLinux users will find gstm in the ArchLinux User Repository: https://aur.archlinux.org/packages/gstm/

• For everyone else, release tarballs are available from Github.

If you're building from a release tarball, you'll need pkg-config, gtk3, libxml2, and intltool along with their associated dev packages. The configure script and makefiles are included in the tarball.

Building direct from the git repo, you'll need the above as well as autoconf (>=2.69) and automake. There is a bash script (autogen.sh) to handle the autoconf/automake work and generate the configure script and various makefiles. Run it, then the usual ./configure && make.

Bugs can be reported using GitHub's Issues tab. Before opening a new issue, try reproducing the problem after building the lastest source from the master branch. Also, take a look through the closed issues to see if it's been reported before. This is doubly important if you're using packages from the ppa; Those tend to lag a bit behind.