In article ,
 The Natural Philosopher  writes:
> I have been using the facility of X apps to fowraed to a remote server.
>
> This is the script I use to start and redirect an X application
> (kaffeine) to a machine that has logged in with ssh
>
> #!/bin/sh
> # start in the right place
> cd /var/videos
> # this fixes some errors that I don't understand
> export $(dbus-launch)
> #detect IP address of remote client
> IP=`echo $SSH_CONNECTION | awk '{print $1}'`
> #redirect pulse audio to it
> PULSE_SERVER=$IP:'4713'
> # set default X display to remote client
> DISPLAY=$IP:0.0
> # DBUS_SESSION_BUS_ADDRESS=""
> export PULSE_SERVER
> export DISPLAY
> #kaffeine > /dev/null 2>&1
> kaffeine
>
>
> On the client machines you need something like
>
> xhost +
> ssh -t myserver pathtomyscript

That's horribly insecure.

Remove the references to DISPLAY above, and just do:

ssh -X -C

to tunnel the X session back over ssh, rather than making the
X server available for the whole world to see what you're doing
and tamper.

> assuming you have passwordless ssh set up.
>
> Ex of gigabit ethernet, this isn't fast enough to play movies, but its
> good enough for most other purposes

--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]

--- SoupGate-Win32 v1.05