Description of problem: I can't start 'vncserver' as a user_r user. The same issue affects Xnest. Version-Release number of selected component (if applicable): policy-1.9.2-10 How reproducible: 100% Steps to Reproduce: 1. Log in as a user_r user. 2. Try to run 'vncserver', 'Xvnc :5', or 'Xnest :5' Actual results: Fails. For Xnest and Xvnc the server is started but since it doesn't have a listener socket no X applications can be displayed on it. Expected results: Should work. For vncserver: audit(1081105249.567:0): avc: denied { name_bind } for pid=2810 exe=/usr/bin/perl src=6005 scontext=tim:user_r:user_t tcontext=system_u:object_r:xserver_port_t tclass=tcp_socket For Xvnc: audit(1081105310.203:0): avc: denied { name_bind } for pid=2818 exe=/usr/bin/Xvnc src=6005 scontext=tim:user_r:user_t tcontext=system_u:object_r:xserver_port_t tclass=tcp_socket For Xnest: audit(1081105195.526:0): avc: denied { name_bind } for pid=2806 exe=/usr/X11R6/bin/Xnest src=6005 scontext=tim:user_r:user_t tcontext=system_u:object_r:xserver_port_t tclass=tcp_socket
Could you try this with setenforce 0 and see what errors are produced? Dan
Xnest/Xvnc: There are no more messages with setenforce 0, just that one.
Could you add ifdef(`xserver.te', ` allow $1_t xserver_port_t:tcp_socket { name_bind }; ') to macros/user_macros.te and see if you can get these tools to work in enforcing mode?
Excellent, all work fine! Thanks!