Providing the X server is allowing TCP domain connections and accepts the MIT-MAGIC-COOKIE-1 over TCP connections, getting the MIT-MAGIC-COOKIE-1 to the remote host is relatively easy. The xauth on the console host can see the MIT-MAGIC-COOKIE-1 and can be used to copy it into the .Xauthority file in the users home directory. Thereafter remote applications will automatically pick it up from the user's (NFS shared) home directory on any other hosts they need to use.
We have seen many of our applications where the overhead of the encryption is simply massive and combined with the latency of the continuous context switching to the SSH process to encrypt the data becomes utterly unacceptable. Granted one particular application involves synchronising video feeds from multiple video camera captures performed by multiple hosts but in this and other roles X11 is up to the task; tunnelled/encrypted X11 is far too slow and is not suitable for purpose.
Providing the X server is allowing TCP domain connections and accepts the MIT-MAGIC-COOKIE-1 over TCP connections, getting the MIT-MAGIC-COOKIE-1 to the remote host is relatively easy. The xauth on the console host can see the MIT-MAGIC-COOKIE-1 and can be used to copy it into the .Xauthority file in the users home directory. Thereafter remote applications will automatically pick it up from the user's (NFS shared) home directory on any other hosts they need to use.
We have seen many of our applications where the overhead of the encryption is simply massive and combined with the latency of the continuous context switching to the SSH process to encrypt the data becomes utterly unacceptable. Granted one particular application involves synchronising video feeds from multiple video camera captures performed by multiple hosts but in this and other roles X11 is up to the task; tunnelled/encrypted X11 is far too slow and is not suitable for purpose.
Regards, Bevis.