Php 5.2.17 -patched

[DirectAdmin Support]

Hello,

Firstly, don't use this.
Php 5.2.17 is end-of-life, and this patched version is only to be used as a last resort for admins or clients who have no choice but to stick with 5.2.17.
No support will be given if there are issues with this code.

It was brought to my attention that there are unofficial patches/fixes for some of the older bugs and security issues with 5.2.17:

1) SVN Checkout the backports version at http://code.google.com/p/php52-backports/
2) Apply Patch #28 to fix SSL issue. http://code.google.com/p/php52-backports/issues/detail?id=28

so what I've done is packaged them up into 5.2.17-patched.

If you must use 5.2.17, then at a minimum, update to this patched version to resolve some of the mentioned issues in the above URLs.

If this works and there is enough demand (I hope there is no demand, and that people upgrade to 5.3 or higher)... then we'll consider adding an options.conf setting for custombuild 1.2.
CustomBuild 2.0 needs php 5.3 or later, so this doesn't apply there.

To install it:

cd /usr/local/directadmin/custombuild
perl -pi -e 's/php5:5.2.17:.*/php5:5.2.17-patched:/' versions.txt
./build php n

Uploaded to files1, so please allow 24 hours for rsync if you're using a different download server.

Use at your own risk.
Don't use this!
Upgrade to php 5.3.

Good luck!

John

 

[ccto]

Hello John,

Thank you very much.

Some users do stick to PHP 5.2, at least, because

- those bought some PHP encoded program, which was encoded in Zend Optimizer, which must be run under PHP 5.2 , and no further support from the developer.
- and many are reluctant to upgrade the program (especially those in-house program where the web designer were not contactable)

 

[scsi]

There is no excuse for anyone to need php 5.2 still. Even 5.3 is eol in march 2014. If someones software isnt being developed anymore then they need to find new software.

 

[kevinb]

There is no excuse for anyone to need php 5.2 still. Even 5.3 is eol in march 2014. If someones software isnt being developed anymore then they need to find new software.

PHP 5.3 is EOL in July 2014 not March.

Kevin

 

[scsi]

It used to be...I guess they pushed it back further.

 

[ViAdCk]

I have tried it on a server with no success. Although it changes the versions.txt file, when I run "./build php n" it still compiles the standard php 5.2.17

 

[scrupul0us]

Make sure to delete any php-5.2.17* folders from the custombuild directory.

That said, does this patched version actually update the version in php -v as 'patched'?

 

[H0sseiN]

I give this error

[root@s1 custombuild]# ./build php n
File already exists:    php-5.2.17-patched.tar.gz
MD5 Checksum on php-5.2.17-patched.tar.gz passed.
File already exists:    php-5.2.17-patched-mail-header.patch
MD5 Checksum on php-5.2.17-patched-mail-header.patch passed.
Found /usr/local/directadmin/custombuild/php-5.2.17-patched.tar.gz
Extracting ...
Done.
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- php-5.2.17/ext/standard/mail.c.original    2009-02-25 23:46:16.000000000 +0800
|+++ php-5.2.17/ext/standard/mail.c     2009-02-25 23:46:56.000000000 +0800
--------------------------
File to patch:

what shoud I input now ?

 

[H0sseiN]

Hey, Admin you forgot to correct mail.c path in patch file !

 

[dudek888]

I confirm that it works on FreeBSD servers without any problem.
Only during installations as mentioned above I had to enter the path to file mail.c "/usr/local/directadmin/custombuild/php-5.2.17-patched/ext/standard/mail.c
And here request, in custombuild when I now update programs dependents of PHP (./ build php n) writing each time the path to file mail.c is a bit cumbersome. Please remove this error if it isn't a problem.
When you can updating custombuil 1.2 so that the command ". / build versions" will be no longer show the message "PHP5 (CGI) 5.2.17-patched to 5.2.17 update is available" ?