John Oliver wrote:
I installed a Java-based app on one of our servers for a user. I'm able
to ssh to the server, export DISPLAY=my.ip.address:0.0 do an xhost + on
my machine (Windows + Cygwin) and launch the app just fine.
It's better to tunnel it over ssh, add:
ForwardX11 yes
ForwardX11Trusted yes
to ~/.ssh/config to forward X over the tunnel, or run ssh -X hostname.
Allowing all hosts via xhost + opens up the possibility of someone
installing, say, a keylogger on your system and it'll be completely
unbeknownst to you unless you monitor 'xlsclients' or something on a
regular basis.
So I ran in to get the program working for him on his Red Hat WS 4
system. I had him ssh to the server, export the display, run xhost + on
his system, and launch the app. It complains about:
When I do an nmap of his machine, port 6000 doesn't show up. iptables
is not running. The server and both of our machines are on the same
subnet.
I'd bet it's a pain in the ass firewall. Make sure iptables isn't
running, or allows through port 6000. Again, a better way is with ssh X
forwarding. Added benefit is all X traffic is now encrypted. Bonus!
Is there some X config that's telling it to not start any sockets or
something? Nothing in /etc/X11/xorg.conf is jumping out at me...
Redhat also has some stupidity where it adds to /etc/hosts a line like
the following:
127.0.0.1 localhost localhost.localdomain somebox somebox.somedomain.tld
Ensure this is not the case. This is broken, broken, broken. Bad redhat,
BAD! NO BISCUIT. It causes things to open up sockets on localhost only.
It's a stupid idea and i wish redhat would stop doing it. But I digress.
let me know if any of this helps.
cheers,
-kelsey
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
