On 10/12/15 08:08, Volker Kuhlmann wrote:
On Wed 09 Dec 2015 19:46:20 NZDT +1300, Ross Drummond wrote:
PS The approved way of forwarding X windows is to do it using SSH. I
only use X forwarding occasionally on my LAN so I reckon the security
provided by SSH is overkill for my situation.
Both ways are fundamentally different and complement each other.
Remote X-server connection (XDMCP):
Connection security: none;
furthermore the X server is exposed as a network service.
Performance: excellent (on LAN), though not all 2D/3D acceleration may
be available (not sure of the precise details).
Desktop functions: available, the whole desktop is remote.
Is sometimes not well supported because of a perceived lack of
use-case.
ssh X forwarding:
Connection security: excellent.
Performance: sucks. Bordering on being useable on a 100Mbit LAN, with
apps that contain their own operating system (like all the mozilla
stuff), or KDE apps. Perfect for straightforward X11 apps like nedit.
Desktop functions: not available; only individual apps can be run.
There's a third option:
Remote desktop:
E.g. VNC type methods.
Connection security: possible, SSL
Performance: lousy. Sluggish even on LAN, and the clients I tried
really sucked - severe graphics errors, dumb layout wasting screen
real estate, unsupported software. Badly designed protocols to top it
off (my impression).
My conclusion: useless.
Volker
I use a program called x2go http://wiki.x2go.org/ its great and easy to
setup, much easier than using x11 forwarding. They have clients for
windows as well.
Bevan
_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
