ANONYMOUS  It would be so great if there were a way for this app to monitor attempts to connect to the local port and automatically bring up the tunnel. I kind of thought that the Auto Connect option would do that, but apparently not--or else I'm an idiot, or both...  
(Version 2.0b3)

ANONYMOUS  I just started using this & it seems to be working fine on OSX 10.37  
(Version 2.0b3)

PAUL JONES  I was looking for a quick way to manage tunnels from my desktop. Ineed to turn them on and off alot. I was using fugu, but typing information each time wasd a pain. Then I built a shell script/men from the command line which was good, butr not ideal. SSH Tunnel Manger was exaclty what I wanted! Thanks, it saved me from needing to write it!

I'm not sure about stability yet. I just started using it. So far it has performed well. I'm curoius to see its handling of timeouts.  
(Version 2.0b3)

ANONYMOUS  This latest version did not work at all with Mac Panther (10.3.7). The preferences files were not loaded and could not be seen by the application. I found an earlier version (1.0.3) did work very well and seems to run without any hitches - although it does occasionally crash when the preferences tab is open, once surfing it works OK.  
(Version 2.0b3)

ANONYMOUS  I am using the old version, I tried the new beta but it had issues when I was editing my configurations. The old version has worked flawlessly for me to date, but I like the features that the new version will bring.. I can't wait for a stable release.  
(Version 2.0b3)

CONSTANTIN  I second David's request for collapsed tunnel detection, auto rebuild, and notification. As I have stated earlier, the code already exists as open-source code in AutoSSH.

B3 seems to be quite stable. I have had no major issues yet, so I'll be using it for now.  
(Version 2.0b3)

ANONYMOUS  Does this handle DSA/RSA Authentication (preferably DSA)? Or does it only handle password? Asking because password can be broken much more easily.  
(Version 2.0b3)

DAVID LAWSON  I too have had frequent problems with collapsed tunnels that were not detected by SSH Tunnel Manager. It's a pity as the tunnel manager is easy to configure and run hidden on startup -- much more elegant than most solutions using scripts.

In addition to better tunnel stability -- and a facility to automatically detect and reopen collapsed tunnels -- it would be nice to have better error reporting. (This is also what makes it hard to write good tunnel scripts.) If I could hide Tunnel Manager and have its dock icon start bouncing whenever the status of a tunnel changed, I would be in tunnel heaven.

None of this changes the fact that this product is an essential utility that is basically well done. As soon as it becomes more robust it will deserve five stars.  
(Version 2.0b3)

ANONYMOUS  This (2.0b2) shows hope!

But until it gets more stable..

back to 1.03 I go.  
(Version 2.0b2)

CONSTANTIN  I stand by my earlier review regarding the new interface. However, for whatever reason the new tunnel manager does not appear to be as stable maintaining tunnels as the older 1.03 client.

I noticed this mainly in extended use - the SSH tunnels would collapse without warning, followed by beachballs of death in the applications dependant on port forwarding (mail, http, etc.)

Rebuilding tunnels after a collapse would not work consistently - even though the application shows a working tunnel (i.e. green status light). My underlying SSH components seem to be OK because I'd still be able to SSH in via the terminal application.

Even closing the tunnel manually and quitting SSHTB would not work. I had to restart the PB before SSHTB would work again. I have reverted to 1.03 in the meantime since being on the bleeding edge has left me SSH-less.

In comparison, version 1.03 allows me to leave the same tunnels open all day, as long as I have some activity every 2 minutes or so. Thus, there seems to be a bug in SSHTB 2.0b that affects my machine (PBG4, OS 10.3.2). Has anyone else had the same issue?  
(Version 2.0b)