>From the SSH man-page:
If the user is using X11 (the DISPLAY environment variable
is set), the connection to the X11 display is automati�
cally forwarded to the remote side in such a way that any
X11 programs started from the shell (or command) will go
through the encrypted channel, and the connection to the
real X server will be made from the local machine. The
user should not manually set DISPLAY. Forwarding of X11
connections can be configured on the command line or in
configuration files.
The DISPLAY value set by ssh will point to the server
machine, but with a display number greater than zero.
This is normal, and happens because ssh creates a "proxy"
X server on the server machine for forwarding the connec�
tions over the encrypted channel.
Ssh will also automatically set up Xauthority data on the
server machine. For this purpose, it will generate a ran�
dom authorization cookie, store it in Xauthority on the
server, and verify that any forwarded connections carry
this cookie and replace it by the real cookie when the
connection is opened. The real authentication cookie is
never sent to the server machine (and no cookies are sent
in the plain).
Thomas Charron wrote:
> As far as I could tell, *IT'S JUST AN SSH SHELL*. There is no tunnel here.
> An ssh shell is quite literally no different from a telnet session between two
> machines. It's an encrypted stream over IP. From one socket to another..
> There is no 'all traffic' involved here..
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
