New PHP packages are available for Slackware 10.2 and -current to fix minor security issues relating to the overwriting of the GLOBALS array.
It has been reported here that this new version of PHP also breaks squirrelmail and probably some other things. Given the vague nature of the security report, it's possible that the cure might be worse than the disease as far as this upgrade is concerned. If you encounter problems, you may wish to drop back to 4.4.0, and I believe that doing so is relatively safe. I understand at least some of the issues are fixed in CVS already, so perhaps another maintainance release is not far off.
Thanks to Gerardo Exequiel Pozzi for bringing the issues with 4.4.1 to my attention so that this additional information could be included here.
Here are the details from the Slackware 10.2 ChangeLog:
+--------------------------+
patches/packages/php-4.4.1-i486-1.tgz: Upgraded to php-4.4.1.
Fixes a number of bugs, including several minor security fixes relating to
the overwriting of the GLOBALS array.
(* Security fix *)
+--------------------------+
Where to find the new packages:
+-----------------------------+
Updated package for Slackware 10.2:
ftp://ftp.slackware.com/pub/slackware/slackware-10.2/patches/packages/php-4.4.1-i486-1.tgz
Updated package for Slackware -current:
ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/n/php-4.4.1-i486-1.tgz
MD5 signatures:
+-------------+
Slackware 10.2 package:
3a86cbe1c07da03ef444e9205e9fefcc php-4.4.1-i486-1.tgz
Slackware -current package:
3a86cbe1c07da03ef444e9205e9fefcc php-4.4.1-i486-1.tgz
Installation instructions:
+------------------------+
First, stop apache:
# apachectl stop
Next, upgrade to the new PHP package:
# upgradepkg php-4.4.1-i486-1.tgz
Finally, restart apache:
# apachectl start (or: apachectl startssl)
+-----+
Slackware Linux Security Team
http://slackware.com/gpg-key
security@slackware.com
It has been reported here that this new version of PHP also breaks squirrelmail and probably some other things. Given the vague nature of the security report, it's possible that the cure might be worse than the disease as far as this upgrade is concerned. If you encounter problems, you may wish to drop back to 4.4.0, and I believe that doing so is relatively safe. I understand at least some of the issues are fixed in CVS already, so perhaps another maintainance release is not far off.
Thanks to Gerardo Exequiel Pozzi for bringing the issues with 4.4.1 to my attention so that this additional information could be included here.
Here are the details from the Slackware 10.2 ChangeLog:
+--------------------------+
patches/packages/php-4.4.1-i486-1.tgz: Upgraded to php-4.4.1.
Fixes a number of bugs, including several minor security fixes relating to
the overwriting of the GLOBALS array.
(* Security fix *)
+--------------------------+
Where to find the new packages:
+-----------------------------+
Updated package for Slackware 10.2:
ftp://ftp.slackware.com/pub/slackware/slackware-10.2/patches/packages/php-4.4.1-i486-1.tgz
Updated package for Slackware -current:
ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/n/php-4.4.1-i486-1.tgz
MD5 signatures:
+-------------+
Slackware 10.2 package:
3a86cbe1c07da03ef444e9205e9fefcc php-4.4.1-i486-1.tgz
Slackware -current package:
3a86cbe1c07da03ef444e9205e9fefcc php-4.4.1-i486-1.tgz
Installation instructions:
+------------------------+
First, stop apache:
# apachectl stop
Next, upgrade to the new PHP package:
# upgradepkg php-4.4.1-i486-1.tgz
Finally, restart apache:
# apachectl start (or: apachectl startssl)
+-----+
Slackware Linux Security Team
http://slackware.com/gpg-key
security@slackware.com