SBC's and ssh's encryptions

Gene Heskett gheskett at
Mon Nov 28 10:52:41 AEDT 2016

On Sunday 27 November 2016 18:21:00 Peter Stuge wrote:

> Gene Heskett wrote:
> > The odroid64 already has an x system running as soon as I log into
> > the odroid64.  Its $DISPLAY is :0
> That's fine. Remember to run xhost +192.168.71.pi on odroid64.
> > the pi cannot open the display on the odroid64.
> Show an error message when starting e.g. xterm on pi.
> > an echo $DISPLAY on the pi shows: (after I've done the commands)
> >
> If the odroid IP is then that is correct.

It is.
> Way off topic now.

Not really, its getting closer to what I wanted to do when I started 
this thread. What I wanted to do was bypass the ssh's encrypt/decrypt 
time killers.

But another network savvy fellow on the emc list says I should get the 
display by running this on the pi:

xauth extract - $DISPLAY|ssh <pi-usr>@<raspi-ip> xauth merge -

which does not update the $DISPLAY var on the pi, it remains at at localhost:10
This was the actual command line:

gene at raspberrypi:~ $ xauth extract - $DISPLAY|ssh gene at xauth merge -
gene at's password: 
gene at raspberrypi:~ $ echo $DISPLAY

This lack of apparent effect is possibly an artifact of my being logged 
into both SBC from a 3rd (this machine) source.

Thank you Peter. Got to get more sleep tonight.

Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <>

More information about the openssh-unix-dev mailing list