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.
If I would want to change the permission in a whole directory tree (many many subdirs everywhere, and file), let's say I want directories to have 755 and regular files to have 644. IIRC I can use umask to mask away some bits and then do a chmod.
My questions are: can I make umask differ between directories and file. And should I do a chmod 777 after making the umask.
umask sets the default permissions that files and directories have when they're created. If my user's umask is 0027 any files or directories I create when logged in as me will be inaccessible to 'others' and not writeable to 'group' and will give full access to 'user' (the extra zero on the end if for setting special permission bits like setuid, setgid etc.).
So to get the effect of the umask subtract 7 from the umask number. For the group permissions in this example 7-2=5 which is read and execute permissions. It will actually create directories with read and execute permission but files with just read permission - its smart enough to know that making files executable by default is unecessary and could lead to security problems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.