Ubuntu
gstm package

[Intrepid] gSTM is no longer working - time out

Bug #293240 reported by Andrew
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gstm (Ubuntu)
Fix Released
Medium
Ryan Niebur

Bug Description

Binary package hint: gstm

After re-installing my computer (going from Hardy i386 to Intrepid amd64), I can no longer use gSTM. The configuration which used to work fine now results in:

Tunnel 'Home' stopped.
Connection timed out during banner exchange

The SSH connection takes a while for this as it has to go through my work proxy (connect-proxy being used). Normal SSH works fine. Is there a setting somewhere to set the timeout?

gSTM Version: 1.2-4

Related branches

lp:debian/squeeze/gstm
Revision history for this message
Andrew (andrew-rw-robinson) wrote :

Our proxy is running a bit faster today and it connected. Perhaps this should be a wish instead of a bug. Either the timeout should be taken from ~/.ssh/config or we should be able to specify it in the gSTM GUI. I was able to SSH from the command-line fine yesterday, so I know it was not a generic SSH client issue.

Revision history for this message
Ryan Niebur (ryan52) wrote :

Well, all that gstm does is run "ssh". So any defaults and options you set in your normal ssh configuration will apply to ssh tunnels created by gstm too. Except that gstm explicitly overrides the timeout, and sets it to 5. I will work on this.

Thanks for the bug report,
Ryan

Changed in gstm:
assignee: nobody → ryan52
status: New → In Progress
Nathan Handler (nhandler)
Changed in gstm:
importance: Undecided → Medium
Revision history for this message
Ryan Niebur (ryan52) wrote :

okay, fix uploaded to Debian.
I dunno when it will be merged into Ubuntu, but ya...:/

Revision history for this message
Andrew (andrew-rw-robinson) wrote :

Awesome, thank you for the quick response

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gstm - 1.2-7

---------------
gstm (1.2-7) unstable; urgency=low

  * Remove gaskpass. gaskpass is just another ssh askpass program, and
    doesn't do anything special. It does not grab focus, which means
    that key loggers can listen in on what you type, aiui. Seeing as how
    it is just reinventing the wheel, I see no reason to keep it around.
    (Fixes LP: #276530, #276517, #276525, #276529, #276534)
  * Do not explicitly set the ssh timeout, as that causes problems on
    slow networks. (Fixes LP: #293240)

 -- Ubuntu Archive Auto-Sync <email address hidden> Mon, 24 Nov 2008 09:48:55 +0000

Changed in gstm:
status: In Progress → Fix Released
Revision history for this message
Andrew (andrew-rw-robinson) wrote :

Any chance on a Intrepid back-port on this? I am not sure what the correct method of requesting a back-port is.

Revision history for this message
Ryan Niebur (ryan52) wrote :

Sorry, I can't help you with that one. I just do Debian stuff, and don't really intend to do anything directly in Ubuntu.

Revision history for this message
Ryan Niebur (ryan52) wrote :

Requested backport in Bug #308068

Revision history for this message
John Dong (jdong) wrote :

Instead of a backport, let's do this as a SRU. The unintrusive bugfix nature of this bug warrants a SRU.

Revision history for this message
Trochee (trochee) wrote :

John Dong: what is an SRU?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.