Mar 1, 2016
see
chad@chad-System-Product-Name:/$ exit
logout
Connection to 192.168.1.25 closed.
bash-3.2$ ssh -Xv chad@192.168.1.25
OpenSSH_6.9p1, LibreSSL 2.1.8
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug1: /etc/ssh/ssh_config line 102: Applying options for *
debug1: Connecting to 192.168.1.25 [192.168.1.25] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /Users/MAC_at_home/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/MAC_at_home/.ssh/id_rsa-cert type -1
debug1: identity file /Users/MAC_at_home/.ssh/id_dsa type 2
debug1: key_load_public: No such file or directory
debug1: identity file /Users/MAC_at_home/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/MAC_at_home/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/MAC_at_home/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/MAC_at_home/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/MAC_at_home/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6 pat OpenSSH_6.6.1* compat 0x04000000
debug1: Authenticating to 192.168.1.25:22 as 'chad'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:zfXl/BD3s9Suz6kSOpSyU6BlPP89FSbPUgDdg3Tcrbs
debug1: Host '192.168.1.25' is known and matches the ECDSA host key.
debug1: Found key in /Users/MAC_at_home/.ssh/known_hosts:2
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering DSA public key: /Users/MAC_at_home/.ssh/id_dsa
debug1: Server accepts key: pkalg ssh-dss blen 433
debug1: Authentication succeeded (publickey).
Authenticated to 192.168.1.25 ([192.168.1.25]:22).
==============
to bring up a complete KDE Environment over SSH,
specifically Gnome and KDE. It should not be a surprise to
you that this can be done, since the desktop Environments run on top of the X Window
System.
On MAC, login as a regular user on one of the terminals.
Enter "xinit".
A small window should appear. In the window, type
in the following:
ssh -p 8400 -l gomer -X -v 192.168.1.2
MAC_at_home$ ssh -Xv chad@192.168.1.25
where -p is the
SSH port your SSH server listens to, gomer is a valid user on
RAT, and 192.168.1.2 is the IP address of RAT.
Enter your password, then enter the following
command: startkde
(of
couse, this assumes that KDE is installed on RAT)
-->this worked to a fashion.
KDE took over the MAC screen and I could not seem to navigate. I eventually found the keys cmd F4 that gives you the launchpd...
--------------------------------Mar 1, 2016
You should see a normal KDE startup, with the exception
of a sound system error. You can safely ignore the sound system
error, as X does not define any mechanism for playing sounds over
the network (Drat!). You should be presented with a typical
KDE desktop work environment. Go ahead and use it! Over
the LAN, the response should be quite good (especially in a 10/100/1000
switched Ethernet environment). You should even be able to play
games like kasteroids
or iagno with no noticeable
delays. gqview
is also a good app to test over the network, as it displays large,
colorful images and lets you manipulate them.
I have even been able to run Xine over X over SSH to watch
VCDs, MPEGs, and QuickTime movies on RAT! Even more amazing,
is that I have been able to run OpenGL 3D-accelerated games like Tuxracer
on X over SSH. There is some noticeable "jitter", since every frame
is being encrypted, sent over the network, then decrypted, but it is
playable. The only thing you have to keep in mind is that the
OpenGL capable hardware and drivers have to be on the X Server side.
In my test, the X Client (which had the tuxracer executable),
did not have a 3D video card or OpenGL drivers, but the machine with
the X Server (and no tuxracer executable), did.
To exit, close all windows and applications, then click
on the "logout" item in the KDE start menu. KDE seems to exit
cleanly, leaving no leftover KDE processes running after you logout. Now
exit from your SSH and xinit sessions.