>On Saturday 26 Mar 2005 17:53, Mikkel L. Ellertson wrote:
The reason has to do with X server security. Normally, only the user that "owns" the current X secession can have programs "connect" to it. Starting an X based program requires that it connect to an X server. Now, the user that is logged to the GUI "owns" the current X secession. He/she/it has the "keys" needed to connect in their home directory. If you use "su" to change to another user, the "keys" are still there. But if you use "su -", or if you change the envirement, then you no longer have the "keys", and the X server will not let you connect. Running "xhost + localhost" or "xhost localhost" tells the X server that any program on localhost can connect without needing the "keys". This is ok for a home system, but is a security risk on a more open system.
That sounds logical, Mikkel, except for two things. One - it doesn't always happen when you try to edit a file as root, and two - it sometimes happens when you are working as user!
Anne
Anne,
I don't know what to tell you. The only thing running
"xhost + localhost" or "xhost localhost" does is allow any X based program on "localhost" to connect to the X server. The only reasion a user would need this would be in the XAUTHORITY shell varable was changed or missing. This should only happen if they start a new "login" shell. You can set the different term programs to start that way, but this is not the default.
Mikkel --
Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup!
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
