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: https://stackoverflow.com/questions/16808813/nginx-serve-static-file-and-got-403-forbidden

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.

  • Markaos@lemmy.one
    21·
    4 months ago

    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

  • Scott@lem.free.asEnglish
    1·
    4 months ago

    The execute bit on directories allows for traversal of the directory (i.e. allows you to cd in), while the read bit allows for listing the directory contents (e.g. ls).