On Tue, 25 Jan 2000, Stephen Ryan wrote:
> (Wow. I actually know how this works; I guess reading all that
> documentation pays off every now and then.)
>
> 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 was just saying more or less that to Paul. I agree that this is what it
does. I still would have exptected it to work.
> 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).
Yeah, I'm inclined to agree. I still would have expected it to work,
but evidently it doesn't. In any case, the easy solution is to just
install (or actually, just configure and run it... it's already there)
sshd on the target system.
--
"Quis custodiet ipsos custodes?" "Who watches the watchmen?"
-Juvenal, Satires, VI, 347
Derek D. Martin | Senior UNIX Systems/Network Administrator
Arris Interactive | A Nortel Company
[EMAIL PROTECTED] | [EMAIL PROTECTED]
-------------------------------------------------
**********************************************************
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
**********************************************************
