After extracting existing concrete5 from a .zip, items have all read write execute chmod rights
Permalink
Hi,
I'm trying to move an existing concrete5 5.7.5.2 installation from /web/concrete/ to the /web/ (root) directory of my own QNAP NAS server. While I'm still figuring out how this could be done the best way, I temporarily moved back the concrete5 CMS to the old directory /web/concrete/.
As a backup, I have created a zip file and extracted it anyway. Now that I have put the concrete5 CMS to the old directory, it works again as a charm. But the folders and files have all rights that could be granted (read / write / execute) - there's no difference anymore. I'm sure there were some reading and executing, but not writing rights applied to certain directories. And of course I don't know which are the right ones to each sub-folders, files etc.
What must be done so that I can be sure that the access to the directories or files isn't vulnerable anymore?
I'm trying to move an existing concrete5 5.7.5.2 installation from /web/concrete/ to the /web/ (root) directory of my own QNAP NAS server. While I'm still figuring out how this could be done the best way, I temporarily moved back the concrete5 CMS to the old directory /web/concrete/.
As a backup, I have created a zip file and extracted it anyway. Now that I have put the concrete5 CMS to the old directory, it works again as a charm. But the folders and files have all rights that could be granted (read / write / execute) - there's no difference anymore. I'm sure there were some reading and executing, but not writing rights applied to certain directories. And of course I don't know which are the right ones to each sub-folders, files etc.
What must be done so that I can be sure that the access to the directories or files isn't vulnerable anymore?
