Re: X access control
- From: Dances With Crows <danceswithcrows@xxxxxxx>
- Date: 23 Apr 2008 16:11:58 GMT
Witek Jarnas staggered into the Black Sun and said:
How can I enable applications from localhost to be run on user's
display? I have to execute "xhost +localhost" everytime I start a
user's session.
Are you *sure* you're doing it right? Most X servers are started with
"-nolisten tcp" these days. The syntax you use now is "xhost +local:",
which allows X clients on machine1 to connect to the X socket in
/tmp/.X11-unix/ on machine1.
export DISPLAY=:0.0 ; [ "$DISPLAY" != "" ] && xhost +
That's not right either. "xhost +" removes all access control, which is
a Very Bad Idea if your X server is listening for TCP.
but it takes [a] long time to log on [when the] X server is not
running. Is there any system wide file of where I can disable access
control for localhost?
No.
If not, how can I configure it correctly ?
See first paragraph. In my tests, a user who does not have access to :0
, sets DISPLAY to :0, and does "xhost +local:" sees the command return
with an error message in < 1 second.
--
I will rule you all with my iron fist. YOU! Obey the fist!
--Invader Zim
My blog and resume: http://crow202.dyndns.org:8080/wordpress/
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
.
- References:
- X access control
- From: Witek Jarnas
- X access control
- Prev by Date: X access control
- Next by Date: vnc does not show *same* screen, it opens a new session instead
- Previous by thread: X access control
- Next by thread: vnc does not show *same* screen, it opens a new session instead
- Index(es):
Relevant Pages
|
|
