Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
I have installed a software that can create multiple daemons that users can use for script caching. But, I`m looking for a way to restrict user access for it`s own daemon. So, basically, x user won`t be able to access y user`s daemon. Also, I would need a way to be able to restrict a user to use multiple daemons. Is this possible ? I saw that grsec patched kernel has this ability and several other security enhancements, but I read some topics about it, and some said it really lacks performance. Is there any other viable solutions ?
PS. I`m using CentOS, so would appreciat some solution that works on it.
for the user x cannot access user y daemon if you can put it in there home dir and chmod 700 to all home dirs.
for the multiple user daemon create a group and add the users to it and chown rootnew group) daemonname
and chmod 770 daemonname
as far as grsec i would recommend staying away from it unless you are really paranoid about security. like me =)
grsecurity is very nice but it takes alot of time to get running exactly how you want it and if you add programs to the system you get to change your policy again and again.
if you want to try out grsec i have a my distro that is almost done and it has grsec built in.
How can one chown a process ? The soft can create multiple streams, a sort of local http server ( but on different ports ) that users can access. So I can`t just chown the file. Waiting for reply. Thanks
sorry bout that. i thought that the certain users just needed to stop/start the daemon. off the top of my head i can not think of a way beside grsecurity or selinux
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.