Re: Tunneling with out a shell or VNC on the other end

Yes and I had considered shell-less tunnels from the very beginning.
I intentionally left it out for the first round of things as such a
connection doesn't really have any visual confirmation of it's
existence beyond a connection listing in the Active Connections.
Rather than deal with the display of a new sort of connection, I put
it off to return to it later. That later is now. The next update is
big one which will include many new features, including this one!
Should be out here pretty soon!

Dean

On Jul 29, 8:14 am, Andres <andres.susar...@gmail.com> wrote:
> So far I've not seen any other discussions touch on this... Dean,
> would you be willing to consider this as a feature idea?
>
> Note that the system in the middle that cannot take a shell is one
> that only bridges the company firewall and verifies my RSA SecureID
> token.  So if I just did ssh to that server, I would enter the secure
> ID token when ssh demands a password, and then I get entered into a
> simple text interface (not a shell) to ssh to a second server inside
> the firewall where the real connection to get work done begins.  Using
> ssh the way I do as described above allows me to enter the token code
> establish several tunnels to various servers inside the firewall,
> without having to seek a shell on the system in the middle, or having
> to have a terminal session on any of the servers inside the firewall.

--
You received this message because you are subscribed to the Google Groups "iSSH/iX11" group.
To post to this group, send email to issh@googlegroups.com.
To unsubscribe from this group, send email to issh+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/issh?hl=en.