Changing file and folder permission?

[sviftrup]

When mambo/joomla creates or edits files and folders it changes ownership of the files to its own. That way I cant delete/change any of those files and folders when i use ftp programs unless i set permissions to 777 which I dont like at all.

Is there any way i can change ownership so ftp programs can do their thing?

thanks in advance.

[joomlahut]

So far there's no resolution to this problem in Mambo, you'll have to ask you host to change the files ownership to your username or run phpsuexec/suexec for apache to create files and folders as user not as apache user.

Actually this should be added to the wishlist as a new feature similar to File/Directory Permissions in global configuration.

[Websmurf]

keep in mind that suexec will have large impact on the performance of your server. Especially with large sites, this will cause problems.

[joomlahut]

phpsuexec/suexec are installed on the server hosting mambohut.com and I haven’t noticed any related performance issues

[bulldog]

So far there's no resolution to this problem in Mambo, you'll have to ask you host to change the files ownership to your username or run phpsuexec/suexec for apache to create files and folders as user not as apache user.

Actually this should be added to the wishlist as a new feature similar to File/Directory Permissions in global configuration.

Ha!  Actually submitted this today as a feature request before reading this post. 

[Vince]

phpsuexec/suexec are installed on the server hosting mambohut.com and I haven’t noticed any related performance issues

As a general rule, running PHP as an Apache module will be faster as the runtime is loaded into memory. However, if you're doing a lot of cgi-based access the phpsuexec may stay loaded in memory anyway, but does use extra resources to run as a cgi module.

The other difference is with webserver permissions. Having PHP as a cgi (phpsuexec) will run under the user's own account. Yes, this means users can more easily manage files as they are 'owned' by them, but it also does carry a risk that websites/personal files are more 'open to exploitation' than under a normal mod_php setup, since the php cgi application has read/write privilages instead of just read-only privileges.

- Vince

[dsmflash]

phpsuexec/suexec are installed on the server hosting mambohut.com and I haven’t noticed any related performance issues

As a general rule, running PHP as an Apache module will be faster as the runtime is loaded into memory. However, if you're doing a lot of cgi-based access the phpsuexec may stay loaded in memory anyway, but does use extra resources to run as a cgi module.

The other difference is with webserver permissions. Having PHP as a cgi (phpsuexec) will run under the user's own account. Yes, this means users can more easily manage files as they are 'owned' by them, but it also does carry a risk that websites/personal files are more 'open to exploitation' than under a normal mod_php setup, since the php cgi application has read/write privilages instead of just read-only privileges.

- Vince

actually, cgi is more secure because the Apache module forces you to chmod to 777 for many extensions.