Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok the main problem: I want to set up xhost such that "xhost +" will not be enabled. I do not want users to be able to just have all hostnames access a system.
The minor problem is that I cannot find where xhost is keeping its list of hostnames that it will allow. The man page said that it would be /etc/X*.hosts but there is no such file that fits into that description. I know it is taking data, because I entered a few hostnames and here is the output that I get:
Code:
[root@cmi321 ~]# xhost
access control enabled, only authorized clients can connect
INET:cmi323.svl.ibm.com
INET:cmi322.svl.ibm.com
Your problem is basically the inverse of mine, but I think it points to the answer for you. There is a startup option for X '-nolisten <proto>', where proto is one of tcp, udp, others that I can't remember.
-nolisten tcp seems to override any xhost settings I apply. So far, I haven't been able to track down where this setting actually originates (and I'd like to remove it). I'd be grateful if someone can point this out.
I use Scientific Linux, which is basically a RHEL clone.
I can't find the config file (or I assume it is a config file) that you are refering to. Where would I find the X startup options (or where would I edit them)? Sorry I'm slow with this stuff.
In my RHEL compatible system (Sceintific Linux), I had to edit
/etc/X11/gdm/gdm.conf
I had to un-comment
# DisallowTCP=true
and change it to
DisallowTCP=false
I hope this can help the original poster, paranoid times
Part of the trick for me was that I was trying to get the effect to take place by sending a SIGHUP to the X server. It needed a full restart to make it take effect.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.