Steve:
Sorry, not exactly: the SSH connection is only secured "in between"
the client and the server. Since its connecting from the same machine to
itself, it's not much extra added security.
The login session between the client and the echoServer has
all passwords encrypted, but subsequent commands on that channel
are not. All data sessions "thru" the echoServer are of course encrypted
end-to-end.
cheers,
Scott
On Jan 19, 2008, at 1:34 PM, Steve Sobol wrote:
> Scott Best wrote:
>
>> What that command does is cause ssh to open a tunnel from the
>> port 443 on the external IP address (66.135.32.141), and securely
>
> So, this secures your login. The session is already encrypted, right?
>
>
>
> --
> Steve Sobol, Victorville, CA PGP:0xE3AE35ED www.SteveSobol.com
> Geek-for-hire. Details: http://www.linkedin.com/in/stevesobol
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
