Recursive execute(x) required to enable nginx to read a directory !?? [ SOLVED ]
from Rick_C137@programming.dev to linux@lemmy.ml on 16 Jul 2024 10:48
https://programming.dev/post/16930149
from Rick_C137@programming.dev to linux@lemmy.ml on 16 Jul 2024 10:48
https://programming.dev/post/16930149
Hi,
I’ve noticed something quite odd, but I don’t know if the problem come from Linux itself or nginx…
In order to grant nginx access to a directory let say your static
see: stackoverflow.com/…/nginx-serve-static-file-and-g…
These parent directories “/”, “/root”, “/root/downloads” should give the execute(x) permission to ‘www-data’ or ‘nobody’. i.e.
but it seem not only the direct parent need to be given XX5 but all the chain
for example
example └── sub1 └── sub2 └── static
it seem you need to set allow others
to read and execute 5
all the parents example, sub1, sub2
Why is that !?? I’ve found it so akward and unsecure !
is there a workaround ?
Thanks.
threaded - newest
It’s a property of how Linux permissions work when applied to a directory.
See this SE post for more info: unix.stackexchange.com/a/21252
Probably a bit of a TL:DR of the other answer, but the short answer is:the execute bit has a different meaning for directories - it allows you to keep going down the filesystem tree (open a file or another directory in the directory). The read bit only allows you to see the names of the files in the directory (and maybe some other metadata), but you cannot open them without x bit.Fun fact, it makes sense to have a directory with --x or -wx permissions - you can access the files inside if you already know their names.
Edit: not a short answer, apparently
Thank you all !
Indeed setting
execute
perm on example, sub1, sub2, staticThe program/user have now access to the directory.
In order words all the parents directory need at least
execute
in order to have access in the targeted directory…Now I gave 751 for static. Meaning than others (here nginx) cannot list the files within. But never the less it works
the static files are appearing when requested (HTTP) but forbidding nginx to list the directory is changing something ? (performance/security)
Thanks