Actually, that brings up another point, that I don't know if it's still
the case.
When you write a file to a specific place, the SELinux contexts are set
for what's usually expected at that file path. e.g. Write a page.html
file in your homespace, and it'll get general context that won't be
readable by a webserver.
If you copied that file to another place, the copy will be written with
the expected contexts for that new place. e.g. If you copied that
page.html to your webserver serving path, the copy will get contexts
that allow it to be web served.
If you moved a file to another place, the original contexts went with
the file. e.g. Your page.html in your homespace with general purpose
contexts ends up in your webserver serving path still with general
purpose contexts that don't allow it to be served.
That kind of thing caused problems for people who migrated various
kinds of data from one point to another, instead of copying it, or
creating it in the right place to start with.
Yup. In the video I linked to earlier, I talk about that problem. It's
an easy mistake to make. Almost always, the solution is to just
restorecon -vR the parent directory and you'll see what it was, and what
it was changed to. Then it starts working.
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
