Quoting Stephen Ryan <[EMAIL PROTECTED]>:
> > I believe earlier he had stated he was manually setting the DISPLAY
> > variable. DISPLAY is where an xclient is going to try to connect,
> regardless
> > of how you initiated the shell.. Usually, in the case of xterm, this
> variable
> > is transparent to the end user, simply becouse xterm sets it up itself..
> The way ssh deals with X connections is to run a proxy X server on the
> machine you are logging into, and to forward all of the requests over
> the encrypted line back to your local display, where the ssh client
> there passes them on to your local X server. The DISPLAY variable that
> is set on the remote machine is not pointing to a real X server, it is
> pointing to ssh. I'm guessing that when you telnet from there and try
> to pass the same DISPLAY variable across the telnet connection, it
> fails because there isn't a real X server behind that DISPLAY, only ssh
> (which has limited X functionality). I don't know if there is a way to
> make ssh accept X connections from other machines or not. I suspect
> that the easiest way around this is really to install sshd on all of
> the client machines you intend to connect to.
Ahh, Ok, so it's functionality of sshd then? I wasn't aware that the daemon
had such capabilities..
In that case, what your saying may be 100% correct. It may be the auth method
sshd supports isn;t one that the client likes, or vice versa..
---
Thomas Charron
<< Wanted: One decent sig >>
<< Preferably litle used >>
<< and stored in garage. ?>>
**********************************************************
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
**********************************************************
