[TYPO3] Changing File Ownership a Requirement for Typo3?

[Christopher]

Hi,

On 4/10/06, Gilles Deacur <tronno22556 at gmail.com> wrote:
> My web host OCCHosting.com is starting to want to charge me $20 per
> incident when I ask them to change file ownership settings to be able to
> have Typo3 run properly.
>
> They cite the lack of quality installation documentation,
> and the "fact" that changing file ownership settings is not a
> requirement to get Typo3 running.
>
> QUOTE:
>
> You can change file permissions, that is all I am doing
> changing ownership is not a requirement, I made limited changes only try
> to conform to their limited doc. but again, it not a requirement to get
> typo3 up and running.
>
> END QUOTE
>
> I'm under the impression that Typo3 does need file ownership set for it
> to run properly, and from their email, it looks like they are telling me
> that I don't need to change file ownerships --only permissions-- to get
> Typo3 running properly.

Based on your messages to the list this week, I have one
recommendation: switch hosts!

In any case, to answer your question, changing ownership is NOT
necessary, but is likely preferable for security purposes (assuming
that suexec is not a factor since if it were, the host would not have
had another group to change files to...)

You _could_ run this:

chmod 777 -R fileadmin typo3conf typo3temp uploads

...but that makes the directories WORLD-writeable; possibly a security hazard.

Usually (and in shared environments, the host will need to do this)
people do this instead:

chgrp -R nobody fileadmin typo3conf typo3temp uploads

...which, I gather, is supposed to be safer though still a problem on
a poorly configured shared host.

Ask your host this:

"Would you prefer that I set file and directory permissions to 777
instead of requesting group changes from support?"

...I know many hosts would do the work (one line of typing!) for free
just to avoid having their clients create world-writeable
directories...


-Christopher