X11 Forwarding

Hi I've been reading this post:

http://raspberry-python.blogspot.co.uk/2012/09/sidekick.html

I'm under the impression this will eliminate the need for VNC if I connect to my pi via ssh on my mac or windows machine. It seems to have been done in debian however and I'm struggling to achieve it in Arch.

So far I've made sure the openssh daemon runs on bootup by enabling it with the systemctl command.
$this->bbcode_second_pass_code('', '# systemctl enable sshd.socket')
I've checked the wiki for opens and have made the following changes to the two configuration files:
$this->bbcode_second_pass_quote('', '
')In /etc/ssh/sshd_config
#AllowTcpForwarding yes
#X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes

In /etc/ssh/ssh_config
#ForwardX11 yes

[karog]

On the Pi in /etc/ssh/sshd_config you need to uncomment X11Forwarding
$this->bbcode_second_pass_code('', '
#AllowTcpForwarding yes
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
')
by removing the # before X11Forwarding.

You don't need to do anything to /etc/ssh/ssh_config

Next from the Mac do
$this->bbcode_second_pass_code('', '
$ ssh -Y ben@PI_IP_ADDRESS

# pi> echo $DISPLAY
localhost:10.0
')
Note -Y rather than -X - see the man page.

Do the echo of $DISPLAY env var. It should be something like the above. If it shows nothing, something is not set up correctly.

Then in the ssh session run some program like xterm and you should get a window on the Mac.

You need to have XQuartz installed. It will start automatically when you run an X client program on the Pi but it is better to start XQuartz first so you don't wait wondering if there is a problem or simply waiting for X to start.

[WarheadsSE]

Also of note: sshd is already enabled, by default, out of the box in Arch Linux ARM

[Axolotl9250]

That's great, thanks, I notice
$this->bbcode_second_pass_code('', 'ssh -X ben@PI_IP_ADDRESS')
works as $this->bbcode_second_pass_code('', '$ ssh -Y ben@PI_IP_ADDRESS

# pi> echo $DISPLAY
localhost:10.0') does. Now I'm looking into getting it set up and running so as it is as secure as I can make it without gettin in way over my head. If both ways work, is one better or more secure than the other? I've already disabled root login, only use protocol 2 and have specified only my username on the pi can login by ssh. I'm currently looking at keys, which I think are used by unix based machines like linux/mac, I've not seen them set up on windows in my reading so far.

Thanks,
Ben.

[harroxelas]

PuTTY can do key auth on window$, but it doesn't support the usual OpenSSH key format, you'll have to convert it to PuTTY's format with PuTTYgen. As for X11 forwarding under window$, I think you'll need something like Exceed to make it work.