1. That's a shame, their blurb seems to mention FTP several times and certainly appears to indicate support.
2. I suppose I'm trying to work out how to identify whether the user is at home or internal, then suitably manipulate their browser's proxy address. Seems like you have managed this?
Quote:
SSL-Explorer’s nEXT (Network Extension) feature offers full network access to corporate resources.
A number of additional tasks can be performed when using nEXT over and above the functionality
offered by a basic, browser-launched SSL VPN tunnel.
|
Ah I see... just reading through the admin guide..
oooh,oooh,ooh...and
Quote:
An SSL Tunnel is simply a connection between two TCP enabled components. All of the data
transmitted over a tunnel is encrypted using the SSL protocol. This is done the same way as other
tunnelling technologies.
For example, a user may wish to create a secure tunnel to a TCP/IP enabled database that exist the
other side of an SSL-Explorer server. First of all, an administrator configures a new SSL-Tunnel that
uses 63389 as its source port and mysql.mycompany.com:3389 as the destination. The user may
then activate this tunnel and then specify localhost as the hostname and the 63389 as the port and
all traffic with then be secured.
|
Now I'm getting it.
Lea