Re: Unable to use X from remote host...
Did you mean to reply on-list? I've copied the list to bring the
discussion back.
On Tue, Oct 16, 2001 at 10:08:16PM -0500, Darryl L. Pierce wrote:
| On Tue, Oct 16, 2001 at 05:10:12PM -0400, dman wrote:
| > On Tue, Oct 16, 2001 at 03:58:03PM -0500, Darryl L. Pierce wrote:
| > | On my desktop machine (running woody) I enable X server access via
| > | "xhost +" before I telnet into another machine. I then redirect that
| > | machine's display via DISPLAY variable back to my desktop and try to
| > | run an X application. But, the remote machines says that it can
| > | _not_ connect to my desktop's X server.
| >
| > Why not put sshd (package 'ssh') on the server and use 'ssh -X' on the
| > client? ssh will then set up the display for you without requiring
| > xhost. As a side benfit, your password for loggin in will be
| > encrypted and also all the X data will be tunneled over the encrypted
| > ssh connection?
|
| I did. It doesn't work. The local machine refuses the X connection, even
| after I've typed "xhost +".
If you use ssh, there is no need whatsoever t ouse use 'xhost'. On
the server side there must be a directive like "X11Forward yes" (or
something similar) in the sshd_config file. IIRC this is the default
for Debian. On the client side you need to either add the "-X" option
on the command line to enable X forwarding, or put
Host *
ForwardX11 yes
to your ~/.ssh/config file.
| > | Has something changed in X, or can someone point me to a
| > | configuration change that will fix this problem?
| >
| > It hasn't changed recently. The default has been for the X server to
| > not listen on any TCP ports for quite a while.
|
| Since potato? It was never the case in potato for me. I only recently (about
| a month ago) upgraded my desktop machine to woody.
I think potato disables tcp listening by default, but I'm not entirely
sure.
-D
Reply to: