While all the functions in SSHTB can be executed with CLI scripts, this has to be the easiest way to secure your connections with SSH. Nothing takes away from the fact that this is a great program for those of us who like to keep their internet connections secure. Lastly, it would have been nice if SSHTB2 could have imported the prior preference file instead of forcing the user to enter the data all over again.
Silly rabbit, you were supposed to hit enter first! If you finish a line and then hit the "add" button, the line gets erased and you get to start over. Also, AutoSSH would re-establish broken connections automatically once the machine is hooked back up to the internet.Ī minor quibble is the somewhat unintuitive data entry for new tunnels.
#SSH TUNNEL MAC FREE CODE#
It would be great if SSHTB could incorporate the open-source code for AutoSSH, since that would eliminate a number of issues like the one mentioned above. IIRC, there are provisions within the SSH protocol to detect broken LAN connections. even three minutes after shutting off my connection to the internet, the tunnel is still being shown as "Connected". However, SSHTunnel is still having trouble detecting when tunnels are broken. It even shows the various port-forwarding connections being made. The new revision adds some great features! The tunnel now shows the connection being built, with several visual cues - red for no tunnel, yellow for tunnel startup, green for working tunnel. Thus, there seems to be a bug in SSHTB 2.0b that affects my machine (PBG4, OS 10.3.2). 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.
I have reverted to 1.03 in the meantime since being on the bleeding edge has left me SSH-less. I had to restart the PB before SSHTB would work again. My underlying SSH components seem to be OK because I'd still be able to SSH in via the terminal application.Įven closing the tunnel manually and quitting SSHTB would not work. Rebuilding tunnels after a collapse would not work consistently - even though the application shows a working tunnel (i.e. 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.) However, for whatever reason the new tunnel manager does not appear to be as stable maintaining tunnels as the older 1.03 client. I stand by my earlier review regarding the new interface.
0 kommentar(er)
