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 just set up a fedora core 3 server and I need users of a group to be hable read and write access within certain directories. How can I set the initial permissions to eg. 770, so that all new files created by a group member will be set to 770 without using the command chmod ?
I have the same issue. I have a group of users who share responsibility for files in some directories. A file created by one user in those directories should be writeable to the others in the group. Is there no way to make this happen without the user running chmod each time? I have set the sgid bit on the directory so that all files created in the directory are owned by the admin group, but that group still only has r-- rights by default.
I'm getting the feeling that this is simply not a solvable problem in Linux. (Bar running a chmod script in root's cron or something.)
If umask is a user setting, then maybe you could change the umask temporarily while doing this admin work with a script, say "webadm -enable" and "webadm -disable", so you get the right rights while working with the relevant files?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.