remote X

Am 25. Jul, 2003 schw=E4tzte Craig White so:

> I'm sure that there's a lot of wisdom in this message but the intended
> recipient doesn't quite get it which is why I am more than receptive to
> a 'howto" point.

That's pretty well what I sent last night :).

> Server is RH9
> Client is RH8
> xauth is indeed installed on both
> X11Forwarding is enabled in /etc/ssh/sshd_config on both
>
> I had figured it to be easier to learn to do this without ssh to
> minimize elements to configure and would have added ssh to the
> configuration after I got it working.

Actually, it's easier to do via ssh.

> Anyway, what I have done this far is...
>
> from cli on client...

For remote X questions please use 'remote' and 'local' to describe the
machines. local is where the monitor is. remote is the machine you're
reaching out to touch.

In X 'client' and 'server' are opposite of what people generally expect.
They're correctly used because the relationship is inverse of expectation.
Because of this using those terms leads to confusion.

> Server - logged in via ssh, as root 'xhost + 192.168.2.100'
>             su - username then 'xterm -display 192.168.1.100'

>
> got the message unable to open display

Unable to open display means that whatever you tried to do did not have a
token to talk to the local display. If you ssh to another machine as one
user, then use 'su -' to switch to another user the other user will not hav=
e
a proper token. The '-' says to throw out the current environment and login
again.

I am certain it used to work just fine by leaving off the -, but today that
is not working properly. The correct way to get this functionality at this
point is probably by using sudo, but you can also access the .Xauthority
file.

Let's get the basic tunnel working, then we can conquer allowing multiple
users to use it.

Is there a reason you can't ssh as the user you're suing to? sshing as root
is a bad thing, IMHO.

> tried 'echo $DISPLAY 192.168.2.100'
> and 'echo $DISPLAY 192.168.2.100:0'
> and 'echo $DISPLAY 192.168.2.100:1'

Those are just going to echo things.

After the initial ssh try 'echo $DISPLAY'. It will probably be
'localhost:10.0'. At that point try running xterm, xeyes or some other
lightweight X application.

If that isn't working kill the current ssh session and ssh in again, but
this time use -v, -vv, or -vvv to get more info about the session.

ciao,

der.hans
--=20
#  https://www.LuftHans.com/    http://www.AZOTO.org/
#  Motorraeder toeten nicht. Motorraeder werden getoetet.