[BlueOnyx:05032] Re: 5106R YUM updates (suPHP)

[Klein Joachim]

Hallo Michael!

Thanks for the implemenation of suPhp.
Is a great extension of blueonyx and make the life much better with 
customers who uses CMS.
I was missing this for years.

But:
I have tested the system with some customers who had problems and the 
was amazed.
One customer found a bug in the settings of /etc/suphp.conf

If a CMS uses a function to upload and resize a image then the resulting 
file gets the permissions
-rw------- 1 XXX_web site1 121450 Jul 13 20:38 test.jpg

If the user uploads a file with ftp then the file gets the following 
permissions
-rw-r--r-- 1 XXX_web site1 121450 Jul 13 20:39 test1.jpg

Then the file test.jpg isn´t readable for the apache-Webserver and the 
image isn´t displayed correct.
If I changes the /etc/suphp.conf from
umask=0077 to umask=0022
then it worked.
Now the customer is testing again.
I know that it is possible to make a php chmod but this cms haven´t 
implement this function.
Joachim Klein



Am 05.07.2010 02:34, schrieb Michael Stauber:
> Hi all,
>
> HTML version of this message is available here:
>
> http://www.blueonyx.it/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=66&cntnt01origid=15&cntnt01returnid=54
>
> The following updates for BlueOnyx 5106R have been released to the (public)
> YUM repository after testing them out and doing some final fixes and
> adjustments:
>
> ==========
>   Package
> ==========
> Updating:
>   base-apache-capstone
>   base-apache-glue
>   base-apache-locale-da_DK
>   base-apache-locale-de_DE
>   base-apache-locale-en
>   base-apache-locale-ja
>   base-apache-ui
>   base-subdomains-capstone
>   base-subdomains-glue
>   base-subdomains-locale-da_DK
>   base-subdomains-locale-de_DE
>   base-subdomains-locale-en
>   base-subdomains-locale-ja
>   base-subdomains-ui
>   base-vsite-capstone
>   base-vsite-glue
>   base-vsite-locale-da_DK
>   base-vsite-locale-de_DE
>   base-vsite-locale-en
>   base-vsite-locale-ja
>   base-vsite-ui
> Installing for dependencies:
>   mod_suphp
>
> Transaction Summary
> ============================
> Install       1 Package(s)
> Upgrade      21 Package(s)
>
> Total download size: 517 k
>
>
> These updates contain the following improvements:
>
> suPHP support:
> ============
>
> suPHP is a special "wrapper" for PHP scripts that allows to execute PHP
> scripts with the UID of the owner of the scripts. The benefit of this is that
> if a PHP script needs to create files, those files will also be created with
> the UID of the owner of the script. So it is no longer necessary to chown CMS
> sites to the UID "apache".
>
> For each site that uses PHP scripts you will have to enable suPHP separately
> if you want to use it. If you don't, then PHP will use the "old" mechanism.
>
> Additionally a new GUI menu has been added under "Site Management" / "Site" /
> "Services". It is called "Web Ownership". This page allows you to chown the
> /web folder of that site to the UID of "nobody" or of an existing siteAdmin.
> Additionally a server administrator can choose to chown to the UID of
> "apache".
>
> PLEASE NOTE:
> --------------------
>
> - If you enable suPHP, then you MUST use the menu entry "Web Ownership" to
> chown the site to the ownership of a siteAdmin of that site. Otherwise PHP for
> that site will not work correctly.
>
> - If you use a third party PHP (such as from Solarspeed.net), then please note
> that enabling suPHP will revert the site back to the (older) onboard PHP. To
> fix this you need an updated PHP package that supports suPHP. A PHP package
> from Solarspeed.net that supports suPHP is "5106R-PHP-5.2.13-SOL2AV.pkg",
> which just has been released.
>
> - suPHP settings of sites are kept if you migrate a site with suPHP enabled
> through CMU. However: You may have to reset the ownerships of the /web folders
> through the GUI, as the folder itself may still be owned by "nobody" after a
> cmuImport. Additionally it is a good idea to run the script
> "/usr/sausalito/sbin/set_default_php_settings.pl" once after the import.
>
>
> base-subdomains:
> ==============
>
> There was an error in the previous "Subdomains" implementation that prevented
> PHP from working on subdomains. This has been fixed. You may have to remove
> and have to re-add the subdomain(s) for this to be fixed, though.
>
>