[BlueOnyx:05641] Re: Permissions issue with suPHP

[Darrell D. Mobley]

> -----Original Message-----
> From: Darrell D. Mobley [mailto:dmobley at uhostme.com]
> Sent: Tuesday, October 26, 2010 12:32 PM
> To: 'BlueOnyx General Mailing List'
> Subject: RE: [BlueOnyx:05636] Re: Permissions issue with suPHP
> 
> If I set the permissions to 644, the CSS files can be edited in the Joomla
> administrative backend, but as soon as they are saved, they are set as
> 555.  At that point, the files are unable to edited and saved in the
> administrative backend OR with an FTP-base editor.  So permissions have to
> be reset from the shell every single edit.
> 
> What is so bizarre about this is you can successfully modify the
> template's index.php in the administrative backend, even though the
> permissions are set to 555, but you cannot edit and save the CSS files.

Ok, more Googling let know that was standard behavior, changing the file
back to 555 when done to protect it.  Even though the file is reported as
unwritable by the GUI, you can still make modifications and it will resave
the file.

> And of course, at 555, you can't edit the template's index.php with the
> permissions set to 555 either.

I guess the solution for those with FTP-based file editors is to simply not
run suPHP?

Also:

> etc/suphp.config file
> 
> Changed unmask from 0077 to 0022
> 
> Does this file get overwritten by Yum?

Anyone know?