Running X Remotely From An S/Key Session
Note that S/Key sessions are not encrypted, so everything you do, including running X clients remotely, can be intercepted by others.
Set DISPLAY
First you must tell the X applications you want to run where your remote machine is. This is a string of the formdomain-name:0.0Where domain-name is the full domain name of your remote machine. If you do not know what that is, an easy way to find out is to finger yourself on the skey server machine:
% finger jcn@in [in] Login Name TTY Idle When Where jcn Jesse Chan-Norris pts/19 2:26 Sat 11:58 bootp-00.caswellIf you are on campus, you'll need to complete the domain name by adding ".brown.edu".
% setenv DISPLAY bootp-00.caswell.brown.edu
Xhost
You must now tell your remote X server to allow X clients from the CS Department to connect to it. The easiest way is with xhost. (X cookie authentication is safer, but a description of it is beyond the scope of this page).Say you have logged into cslab5e. You can allow X clients run there to connect to your remote X session by doing this on your remote machine:
% xhost +cslab5eNote that this will allow all clients run on that machine to connect, including clients run by other people!
| Page Owner: Dorinda Moulton | Last Modified: Mon Aug 28 17:06:56 2000 |