Aaron Kulkis wrote: > Terje J. Hanssen wrote: >> >> Suggestions: >> >> 1. Frontend GUI client - Backend server: >> The YaST frontend GUI client should be easy and secure to run optional >> on another machine, on a LAN or remotely over Internet. This for all >> admin/config tasks on servers and workstations as well as installing >> Linux if possible. While keeping the existing VNC solution, maybe a >> browser based interface similar Webmin and/or some a kind of a >> fullfledged thin client (NX) are useable. > > since YaST is an X windows program it ALREADY has that capability. > > All you have to do is change the DISPLAY environment variable > to that of another X display, and then, on that display, run > an xhost command to allow programs running from other machines > to show their windows on that display, and YaST *WILL* do > exactly what you say. > > The problem here is not a lack of capability with the current > design, merely a lack of knowledge on your part about how to > display an X windows program on a remote host. > > $ xhost + > $ ssh remote_machine -l root > password: > > # yast2
Well, "xhost +" has been a known security issue for a while. Indeed I left this method 15 years ago on Solaris. http://laurentschneider.com/wordpress/2007/03/xhost-is-a-huge-security-hole.html Beside it is neither necessary. A directly remote ssh login to start yast2 with X-forwarding does also work this way from a root terminal: # ssh IP_adr -X /sbin/yast2 Root Password However, my point(s) was that YaST needs a browser based interface and a fast lightweight crossplatform network client (i.e like NX). As also mentioned, Suse in general needs NX to run the whole desktop or X-apps remotely with deserved speed that competes with Citrix or RDP in the Windows world. --Terje -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
