SSH - serving programs to thin clients

[dedanna1029]

Bloody updates But now life is good again

HA HA HA. And you have this conspiracy thinking going on that I've got some sort of "super duper special customized weird to everyone" setup, even when I've proven time and time again that it was updates.

Phooey on you-ey Boss. *shakes finger at you

I'm wondering if I love you any more.

[rolf]

Ah this has been annoying me for some time now. And FINALLY I found the reason.
On the server side (the remote box):
In /etc/ssh/sshd_config I needed to forward X11.
Like this:

Code: Select all

.....
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes  <-----------!!!!!!!!!
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
......
                       

Bloody updates But now life is good again
restart X with

Code: Select all

sudo /etc/rc.d/sshd restart

(You might need to replace rc.d with init.d - or simply reboot).

Yah duh!!

On the thin client, where sshd is running, I changed two lines in /etc/sshd_config (I believe the commented lines are default configuration; I uncommented, switched no to yes, yes to no, following what the sshd_config manual said):

Code: Select all

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes    <--------THIS ONE, RIGHT HERE, TOL' YOU SO, HE-L-L-L-O-O-O!!!!!!!!!!!!
#X11DisplayOffset 10
X11UseLocalhost no
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no


Then `kill -1 <pid of sshd>` sends SIGHUP to sshd, causing it to restart and read the configuration anew. Now, time to rock and roll!

Code: Select all

[rolf@localhost ~]$ ssh -f -Y root@192.168.1.50 /usr/local/bin/ppm
root@192.168.1.50's password:
[rolf@localhost ~]$ /usr/bin/xauth:  creating new authority file /root/.Xauthority
X11 connection rejected because of wrong authentication.
X connection to puppypc:10.0 broken (explicit kill or server shutdown).
/usr/local/petget/filterpkgs.sh: line 91: kill: (19857) - No such process
X11 connection rejected because of wrong authentication.
The application 'gtkdialog3' lost its connection to the display puppypc:10.0;
most likely the X server was shut down or you killed/destroyed
the application.


Off to google on that authentication error, which gave me, among other things, this:

If you encounter X11 connection rejected because of wrong authentication error after logging to an UNIX/Linux host through ssh with X11 forwarding option, -X, check your /etc/inet/hosts file for multiple localhost entries; and remove the unnecessary ones.

For example, my /etc/inet/hosts has the following entries when the xclock failed with an X11 connection rejected .. error.

remotehost% cat /etc/inet/hosts

127.0.0.1 localhost
::1 localhost
10.2.211.150 sunfiret2000 loghost


Removing the 2nd line, ::1 localhost, fixed the issue.

In Puppy, Mandriva, too, I think there is /etc/hosts, which looked like this:

Code: Select all

127.0.0.1 localhost puppypc
192.168.1.1 pc2
192.168.1.2 pc3
192.168.1.3 pc4

On a hunch, I removed the 'puppyrc' entry and

Code: Select all

[rolf@localhost ~]$ ssh -f -Y root@192.168.1.50 /usr/local/bin/ppm
root@192.168.1.50's password:
[rolf@localhost ~]$

Thanks for the tips and tricks!

[viking60]

To much fleinsopp!

[rolf]

Yeah, I know. It's just a coincidence, really, who can remember something from last month that might be relevant today?
Especially when fleinsopps are in season

[viking60]

Yeah fleinsopp is traditional Berserk food and makes us ferocious

[rolf]

[viking60]

ROFLMAO