remote gui with ssh

[Rashkae]

Jared Greenwald wrote:
> Dude, I don't really understand what exactly you are trying to accomplish,
> but this seems like the least efficient and highest-bandwidth method.
> Passing Gnome desktop information across ssh connections is about as high a
> bandwidth operation as there could be.  You could generate huge amounts of
> lag due to the large amounts of data being passed - even on the same local
> network.  Also, there is a reason for turning off the DissallowTCP option as

Actually, the bandwidth usage of running remote X desktops is so small
as to be almost un-noticeable.  Unfortunately, X really doesn't like
network latency at all, and you'll find the desktop nigh unusable on any
connection with more than 1 or 2 ms latency.  Even a local WiFi
connection is painful.  so unless your hosts are on the same Ethernet,
then tightvnc is the way to go for this.  Note that it's been my
experience that the default ubuntu gnome sessions will not work over
tight vnc unless you disable the gnome-settings keyboard and mouse
plugins.  You can do this from gconf-editor (apps ->
gnome-settings-daemon...)



> it is highly insecure.  If this is the setting I'm thinking of, it allows
> the trusted-ness of a remote system to be spoofed by any system thus
> allowing any system on a given network access to running remote applications
> on your system without any serious authentication.

That's a bit of an exaggeration.  The security concern of X forwarding
is that root user of the remote system can monitor your local X session.
Not really a problem if the user is the administrator of both systems.