Post a Comment
I do love Slackware too, but am very concerned about suggesting:
xhost +
to allow "root" to start x-window applications. 8-(
Much better alternatives are:
"xauth extract ..." and "xauth merge .."
or, even better
"ssh -X root@localhost"
The problem with "xhost +" is, that it allows *everyone on the net* to do whatever he/she likes to your X-Server:
- copy the desktop to his/her machine
- read the contetent of all your windows
- close every window on your machine
- send every window to your machine (forged root logins)
- ...
Even if you are not paranoid, it doesn't mean they're not after you. ;-)
"xhost" is *defenetly* a bad idea!
The wrong idea with "xhost" is that it is "hostbound", like rhosts and rsh/rlogin/...
This should not be used!
Whats wrong with using *secure* tools?
"xauth" is more secure than "xhost" because it is "userbound" and "ssh -X root@localhost" is even more secure and even *more convinient*.
Please take a look at http://www.tldp.org/HOWTO/Remote-X-Apps.html
The big risk with "xhost" is that the machine doesn't have to authenticate itself, in contrast to userbound authenication.
*Every* user on a accepted machine can abuse the X-Server: nobody, root, crackerjack, whatever.
But why bother with beeing logged in: Lets rename my machine, so it is allowd to mess with the X-Server.
Doesn't work? Let's send forged packages, that will do...
Even "xhost +localhost" is a bad idea, because it opens a gaping security hole.
Use "xauth" or "ssh -X root@localhost". If you generate ssh keys you can even log into root *without* password. This is *secure* (!) as long as you keep your privat ssh key secure.
Though I don't recommend this, it is much better than using "xhost".




