[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: separating x client from x server



That's right. The program you're running *is* the X client, and it needs an X server to display its stuff on. Usually it uses the DISPLAY environment variable to find it.
[...]
One way that is apparently compatible with today's paranoia appears to be to use an option on ssh (I believe it's ssh -X) to get ssh to carry the X protocol. I'm not sure of the details, except that it appears to require configuration on both the client and server side.


Where you sit:
ssh-client, X-Server
/etc/ssh/ssh_config
ForwardX11 yes
that way you dont have to say ssh -X bla bla

on the other side:
ssh-server, X-Client
/etc/ssh/sshd_config
X11Forwarding yes

Btw.
If you are not used to ssh,
you should use keys.
If you are used to, you now thing: of course. :-)

1) Create a key: ssh-keygen -t dsa
2) copy public key to other pc: ssh-copy-id user@host
3) ssh-add [file] (asks password)
4) ssh user@host (without password)

If your user is the same on both machines, you don't have
to mention the user, so its not user@host but just host.

There are are of course lots of options for the different ssh
programs.
If you want to use it a lot, then you perhaps would like
to use libpam-ssh.
If you have the same password for your system (where you sit)
and for the key, then you can setup your system to
use the password you enter at login for your
ssh-agent and that way you only have to enter
that password at the login.
And not for every ssh or at least once for the ssh-agent.

If you are interested....I can tell you more. Just ask.

Cu,
Andreas



Reply to: