Forums

Concrete creating files as owner:group "apache"?

Permalink
I've installed concrete to test and noticed that as part of the process I've ended up with temporary files which have been set to owners/permissions that are outside of the control of the user account. Is this correct behaviour? Seems, a bad idea. A sudo will get rid of them, but what about virtual hosting users? They'd be kinda' screwed without opening a dialogue with the owners...

[popecix@axiom stylized]$ ls -al
total 32
drwxr-xr-x 3 apache apache 4096 Apr 29 07:20 .
drwxr-xr-x 3 apache apache 4096 Apr 29 07:20 ..
-rw-r--r-- 1 apache apache 496 Apr 29 07:20 controller.php
-rw-r--r-- 1 apache apache 12034 Apr 29 07:20 icon.png
-rw-r--r-- 1 apache apache 143 Apr 29 07:20 LICENSE.TXT
drwxr-xr-x 3 apache apache 4096 Apr 29 07:20 themes
[popecix@axiom stylized]$ pwd
/home/popecix/public_html/concrete/files/tmp/1335702039/stylized
 
mesuva replied on at Permalink Reply
mesuva
I don't think this would be concrete5 changing or creating files as a particular user. When PHP creates a file, it creates it as the same user as what PHP is running as.

In the case of your example, those files don't look like temporary files, they look like files that are part of the standard install. So it's the process on how they were created that determines who owns them, whether it be manually or via some automatic script.

On my servers, all my concrete5 files, the ones I upload and the ones created by concrete5 are set to have my user account as the owner.

Ultimately, it's it comes down to how your host has been (mis)configured.
popecix replied on at Permalink Reply
*shrug* Those files were left over. I had three subdirs (all with purely numeric names) in the files/tmp directory that had similar ownership changes.

It was all done by a pretty standard install, download, unzip, setup...left with those.

Just thought it would be worth pointing out in case it was a bug or anyone else ran into it.

Glad yours is working fine.