This update covers PHP, PHP-Eaccelerator, Suhosin, and PHP-Sqlite2. This is primarily a bugfix update.
Full Changelog:
http://www.php.net/ChangeLog-5.php#5.2.14
To upgrade:
yum upgrade php
[atomic] PHP 5.2.14
Re: [atomic] PHP 5.2.14
FYI: Updated php 5.2.14 (from 5.2.13) on LAN/development server last night which runs a few cron backups w/mail confirmation overnight. This morning noticed messages not delivered. Checked mail server logs and "p_s: something to block! (Disallowed characters found in MIME headers)" in qmail-queue.log. Examined the quarantined message, it has extra header: "X-PHP-Originating-Script: 10001:script.php^M" inserted before php custom headers.
Bug fix #50907 X-PHP-Originating-Script adding two new lines in *NIX not resolved by this release?
Never had the problem before update... fixed it by editing php.ini and commenting out
BTW: there was no prompt about php.ini.rpmnew during yum upgrade. Will check on production server after php upgrade to see if it is added and make alteration before restarting Apache.
Hope it may be of help to others...
Bug fix #50907 X-PHP-Originating-Script adding two new lines in *NIX not resolved by this release?
Never had the problem before update... fixed it by editing php.ini and commenting out
Code: Select all
;mail.add_x_header = On
Hope it may be of help to others...
Re: [atomic] PHP 5.2.14
I got this notification email when updating php...
OSSEC HIDS Notification.
2010 Jul 27 16:36:19
Integrity checksum changed for: '/etc/php.ini.rpmnew'
OSSEC HIDS Notification.
2010 Jul 27 16:36:19
Integrity checksum changed for: '/etc/php.ini.rpmnew'
Re: [atomic] PHP 5.2.14
That's OK.
When ossec says checksum changed, it basically means the file has changed. So you'll see it all the time when you upgrade your system (e.g. centos 5.4 to 5.5 or whatever) and when you upgrade important components.
In this case you had a php.ini.rpmnew from a previous upgrade. That file was overwritten when you installed the latest php, and ossec noticed and notified you. I'm not sure why it would be interested in a .rpmnew file, but maybe it looks at everything in /etc or looks for php.ini.*
Faris.
When ossec says checksum changed, it basically means the file has changed. So you'll see it all the time when you upgrade your system (e.g. centos 5.4 to 5.5 or whatever) and when you upgrade important components.
In this case you had a php.ini.rpmnew from a previous upgrade. That file was overwritten when you installed the latest php, and ossec noticed and notified you. I'm not sure why it would be interested in a .rpmnew file, but maybe it looks at everything in /etc or looks for php.ini.*
Faris.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
Re: [atomic] PHP 5.2.14
Note that this is not a guarantee that your php.ini wasn't replaced. If you never modified the standard version from the last install, the upgrade is just going to replace php.ini with the standard version for the new package. (This is not necessarily true for every package, but can be configured in the SPEC file for the package.)Kalimari wrote:BTW: there was no prompt about php.ini.rpmnew during yum upgrade.
Lemonbit Internet Dedicated Server Management